Triple
T24352324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CA 134 |
E613824
|
entity |
| Predicate | isPartOfNamedSegment |
P82192
|
FINISHED |
| Object | Ventura Freeway corridor |
—
|
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: Ventura Freeway corridor | Statement: [CA 134, isPartOfNamedSegment, Ventura Freeway corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNamedSegment Context triple: [CA 134, isPartOfNamedSegment, Ventura Freeway corridor]
-
A.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
B.
hasSegmentWith
Indicates that an entity contains or includes at least one segment that satisfies a specified condition or matches a given segment.
-
C.
isSpaceSegmentOf
Indicates that one spatial region or segment is a constituent part or subdivision of a larger spatial extent or segment.
-
D.
isNamedSectionOf
chosen
Indicates that one entity is a specifically named section or subdivision that forms part of another entity.
-
E.
hasSegmentFrom
Indicates that something includes or contains a segment that originates from or is derived from another specified source.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293467a508190937b9614870e243e |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:59 a.m.