Triple
T24069324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twentysix Gasoline Stations |
E596180
|
entity |
| Predicate | sequenceStructure |
P86682
|
FINISHED |
| Object | linear sequence along Route 66 |
—
|
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: linear sequence along Route 66 | Statement: [Twentysix Gasoline Stations, sequenceStructure, linear sequence along Route 66]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequenceStructure Context triple: [Twentysix Gasoline Stations, sequenceStructure, linear sequence along Route 66]
-
A.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
B.
seriesStructure
chosen
Indicates how parts or installments are organized and related within a larger series or sequence.
-
C.
encodingStructure
Indicates the structural scheme or format used to encode information or data.
-
D.
branchStructure
Indicates how the parts of a branching system are organized and connected relative to one another.
-
E.
sequenceDirector
Indicates that one entity serves as the director responsible for overseeing or managing a particular sequence associated with another entity.
- 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_69e288c25c008190850cf447940ab181 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db15866c8190ab931216b8d9c57f |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:41 p.m.