Triple
T35730266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Chase chicane |
E1032731
|
entity |
| Predicate | cornerSequence |
P183866
|
FINISHED |
| Object | right-left-right |
—
|
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: right-left-right | Statement: [The Chase chicane, cornerSequence, right-left-right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cornerSequence Context triple: [The Chase chicane, cornerSequence, right-left-right]
-
A.
cornerRepresents
Indicates that a particular corner in a structure, diagram, or space stands for or symbolizes another element, concept, or feature.
-
B.
eraSequence
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
C.
lapDirection
Indicates the direction or orientation in which a lapping or overlapping action occurs between entities.
-
D.
coordinatesAcross
Indicates a relationship where one entity organizes, aligns, or manages activities or elements that span or involve multiple distinct areas, groups, or domains.
-
E.
successorAlignment
Indicates that one entity’s alignment, orientation, or configuration directly follows and is determined by that of another entity in a sequence or progression.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.