Triple
T27832563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 730 in Oregon |
E703142
|
entity |
| Predicate | isShortSegmentOf |
P81199
|
FINISHED |
| Object | U.S. Route 730 |
—
|
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: U.S. Route 730 | Statement: [U.S. Route 730 in Oregon, isShortSegmentOf, U.S. Route 730]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isShortSegmentOf Context triple: [U.S. Route 730 in Oregon, isShortSegmentOf, U.S. Route 730]
-
A.
isShortestStateSegmentOf
Indicates that one state segment is the minimal-length segment among all segments that could represent that same portion of a state or process.
-
B.
appearsInSegmentOf
Indicates that one entity occurs within, or is featured as part of, a specific segment or subsection of another entity.
-
C.
isSubsegmentOf
chosen
Indicates that one segment is entirely contained within and forms a continuous part of another, larger segment.
-
D.
hasSegmentOn
Indicates that one entity includes or occupies a specific segment or portion on another entity (such as a line, path, or sequence).
-
E.
isSpaceSegmentOf
Indicates that one spatial region or segment is a constituent part or subdivision of a larger spatial extent or segment.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6389cf96c8190a045e3c53f83f3cd |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:57 p.m.