Triple
T37440105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octavia Street |
E930391
|
entity |
| Predicate | hasTerminusConnection |
P97300
|
FINISHED |
| Object | Central Freeway |
—
|
NE NERFINISHED |
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: Central Freeway | Statement: [Octavia Street, hasTerminusConnection, Central Freeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminusConnection Context triple: [Octavia Street, hasTerminusConnection, Central Freeway]
-
A.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
B.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
C.
hasOppositeTerminus
Indicates that one terminus (end point) of an entity is directly opposite or facing the terminus of another entity.
-
D.
connectsTerminus
chosen
Indicates that one entity serves as a terminus that is directly linked or joined to another entity.
-
E.
hasSubTerminal
Indicates that an entity includes or is associated with a subordinate or lower-level terminal element within a hierarchical structure.
- 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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 3, 2026, 4:17 p.m.