Triple
T24845124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA 110 |
E621724
|
entity |
| Predicate | hasHistoricSegment |
P160886
|
FINISHED |
| Object | Arroyo Seco Parkway |
—
|
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: Arroyo Seco Parkway | Statement: [CA 110, hasHistoricSegment, Arroyo Seco Parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricSegment Context triple: [CA 110, hasHistoricSegment, Arroyo Seco Parkway]
-
A.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoricalArc
Indicates that something unfolds over time in a way that forms a coherent, meaningful historical development or narrative.
-
D.
hasHistoricalSection
Indicates that something includes a dedicated part or segment that presents historical information or context.
-
E.
hasHistoricTerminal
Indicates that an entity possesses or is associated with a historically significant terminal facility or endpoint.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 18, 2026, 5:19 a.m.