Triple
T30709671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 5 in Oregon |
E781855
|
entity |
| Predicate | openedAsInterstateEra |
P42060
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Interstate 5 in Oregon, openedAsInterstateEra, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsInterstateEra Context triple: [Interstate 5 in Oregon, openedAsInterstateEra, mid-20th century]
-
A.
openedAsInterstateDesignation
Indicates that a roadway or route first began operation under an official interstate highway designation.
-
B.
openingEra
chosen
Indicates the historical period or era during which something (such as a structure, institution, or work) was first opened or began operation.
-
C.
hasInterstate
Indicates that there exists an interstate connection or highway link between the related entities.
-
D.
signedAsInterstate
Indicates that an agreement, contract, or arrangement has been formally executed between parties located in different states or jurisdictions.
-
E.
federalRecognitionEra
Indicates the historical period during which an entity holds or is granted official recognition by a federal government.
- 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_69f224abfcf081909492e64d3cc35262 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 8:35 p.m.