Triple
T13288576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Dipper |
E316504
|
entity |
| Predicate | hasTypeOfCorner |
P109336
|
FINISHED |
| Object | left-hand turn |
—
|
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: left-hand turn | Statement: [The Dipper, hasTypeOfCorner, left-hand turn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfCorner Context triple: [The Dipper, hasTypeOfCorner, left-hand turn]
-
A.
hasCorner
Indicates that one entity possesses or includes a corner that is part of or associated with another entity.
-
B.
hasTypeOfCross
Indicates that an entity possesses or is associated with a specific type or style of cross.
-
C.
locatedAtCornerOf
Indicates that one entity is positioned at or forms the corner where two or more boundaries, edges, or intersecting paths meet.
-
D.
hasSlowCorners
Indicates that an entity possesses corners or turning points that are navigated or traversed at a relatively low speed.
-
E.
cornerComplexType
Indicates a relationship where something is positioned, formed, or structured at or around a corner in a complex or composite manner.
- F. None of above. chosen
Provenance (4 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69d99cf7f9c48190a6a4f452b4a2aefa |
completed | April 11, 2026, 12:59 a.m. |
Created at: April 9, 2026, 9:27 p.m.