Triple
T19568813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alaska Route 11 |
E489655
|
entity |
| Predicate | terminusAreaUse |
P136614
|
FINISHED |
| Object | oil production |
—
|
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: oil production | Statement: [Alaska Route 11, terminusAreaUse, oil production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusAreaUse Context triple: [Alaska Route 11, terminusAreaUse, oil production]
-
A.
cityCenterTerminusArea
Indicates that the referenced area serves as the terminus or end-point of a route or line located in or at the center of a city.
-
B.
terminusCity
Indicates that a transportation route or service ends or has its final stop in a particular city.
-
C.
terminusRegion
Indicates the region or area where something (such as a route, line, or process) ends or reaches its final point.
-
D.
hasCentralAreaUse
Indicates that an entity’s central area is used or designated for a particular function or purpose.
-
E.
terminusStation
Indicates that a station serves as the final endpoint or terminal stop for a given route or service.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63f7a74e88190a58d5274050a7d32 |
completed | April 20, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:42 p.m.