Triple
T25550738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 84 (nearby) |
E640431
|
entity |
| Predicate | providesRegionalConnectivity |
P99269
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Interstate 84 (nearby), providesRegionalConnectivity, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesRegionalConnectivity Context triple: [Interstate 84 (nearby), providesRegionalConnectivity, true]
-
A.
connectsPortRegion
Indicates that one entity serves as a linkage or interface between a specific port and a defined region.
-
B.
connectsProvinceOrRegion
Indicates that one entity serves to link or provide a connection between a specific province or region and another entity.
-
C.
cloudRegionAvailability
Indicates the availability status of a service or resource within a specific cloud region.
-
D.
operatesBetweenRegion
Indicates a relationship in which an entity conducts operations or provides services that connect or span between two distinct regions.
-
E.
hasRegionalServices
chosen
Indicates that an entity provides or is associated with services that operate within a specific geographic region or set of regions.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 3:36 p.m.