Triple
T14137368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I |
E350332
|
entity |
| Predicate | denotesPosition |
P36701
|
FINISHED |
| Object | first |
—
|
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: first | Statement: [I, denotesPosition, first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denotesPosition Context triple: [I, denotesPosition, first]
-
A.
representsPositionOn
Indicates that one entity specifies or defines the spatial or logical position of another entity within a given context.
-
B.
positionOn
Indicates that one entity is located on top of or at a specific place along the surface or extent of another entity.
-
C.
refersToPosition
chosen
Indicates that one entity makes reference to, or is associated with, a specific position or location of another entity.
-
D.
expressedPosition
Indicates that an entity has stated, articulated, or made known a particular stance, opinion, or viewpoint on some matter.
-
E.
positionDescribed
Indicates that a position, location, or spatial arrangement of an entity is explicitly specified or characterized, typically in descriptive terms.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610fb86c81909eb26bf9c13696ca |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:33 a.m.