Triple
T13054498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giant-Man |
E327534
|
entity |
| Predicate | fieldOfPrimaryUser |
P63305
|
FINISHED |
| Object | biochemistry |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: biochemistry | Statement: [Giant-Man, fieldOfPrimaryUser, biochemistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfPrimaryUser Context triple: [Giant-Man, fieldOfPrimaryUser, biochemistry]
-
A.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
B.
primaryUserType
Indicates the main or dominant category of user associated with an entity or interaction.
-
C.
primaryField
chosen
Indicates the main area of focus, discipline, or domain most centrally associated with an entity.
-
D.
primaryUserOrganization
Indicates that an organization is the main or primary organization with which a given user is associated.
-
E.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.