Triple
T8388593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dasher |
E197882
|
entity |
| Predicate | listedAlongside |
P25756
|
FINISHED |
| Object | Dancer |
—
|
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: Dancer | Statement: [Dasher, listedAlongside, Dancer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listedAlongside Context triple: [Dasher, listedAlongside, Dancer]
-
A.
appearsAlongside
chosen
Indicates that two entities are present or occur together in the same context, setting, or instance.
-
B.
playedAlongside
Indicates that two or more entities participated together at the same time in a shared activity, performance, or event.
-
C.
recognizedAlongside
Indicates that two or more entities are acknowledged, identified, or honored together in the same context or occasion.
-
D.
builtAlongside
Indicates that one entity was constructed next to or in parallel with another entity, typically during the same or a closely related time period.
-
E.
isRankedAlongside
Indicates that two or more entities share the same or very similar rank, status, or position within a given ordering or hierarchy.
- 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_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb81090f688190a3a8d1680383c361 |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.