Triple
T22743432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Izzy |
E562479
|
entity |
| Predicate | positionInSequenceRelativeTo |
P137790
|
FINISHED |
| Object | after Cobi |
—
|
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: after Cobi | Statement: [Izzy, positionInSequenceRelativeTo, after Cobi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSequenceRelativeTo Context triple: [Izzy, positionInSequenceRelativeTo, after Cobi]
-
A.
relativePositionInGroup
Indicates the spatial or ordered placement of an entity within a defined group relative to the other members of that group.
-
B.
hasSequencePosition
chosen
Indicates that an element occupies a specific position or order within a sequence.
-
C.
positionInSet
Indicates that an entity occupies a specific position or rank within an ordered set or collection.
-
D.
positionInAvatarSequence
Indicates the specific ordered position an avatar occupies within a defined avatar sequence.
-
E.
positionAt
Indicates that one entity is located at, or occupies, a specific spatial position relative to another entity or reference frame.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17974c3208190ae1d6b05639cc942 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.