Triple
T33706484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Illinois Route 390 |
E863605
|
entity |
| Predicate | originallyConstructedAs |
P3565
|
FINISHED |
| Object | freeway |
—
|
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: freeway | Statement: [Illinois Route 390, originallyConstructedAs, freeway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyConstructedAs Context triple: [Illinois Route 390, originallyConstructedAs, freeway]
-
A.
originallyBuilt
Indicates that one entity was the first or initial builder or constructor of another entity.
-
B.
constructedAs
chosen
Indicates that one entity is built, formed, or created in the manner, structure, or configuration specified by another entity.
-
C.
originallyBuiltUnder
Indicates that something was first constructed during the rule, authority, or administration of a particular person, group, or regime.
-
D.
originalConstructionFor
Indicates that one entity was the initial or first-built structure, design, or form intended for use by another entity.
-
E.
originallyPresentedAs
Indicates that one entity was first introduced, described, or characterized in the form or manner specified by another entity.
- 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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a034ca1a8d88190bd44f33814436e59 |
completed | May 12, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_6a034b591f2481908e05562841c9a3c2 |
completed | May 12, 2026, 3:46 p.m. |
Created at: May 1, 2026, 1:43 a.m.