Triple
T1239691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Eustis, Virginia |
E26629
|
entity |
| Predicate | hasTransportationFocus |
P5323
|
FINISHED |
| Object | surface transportation |
—
|
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: surface transportation | Statement: [Fort Eustis, Virginia, hasTransportationFocus, surface transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportationFocus Context triple: [Fort Eustis, Virginia, hasTransportationFocus, surface transportation]
-
A.
hasTransitFocus
chosen
Indicates that something is oriented toward, prioritizes, or is primarily concerned with transit or transportation services.
-
B.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
C.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
D.
hasPublicTransitProvider
Indicates that a place or region is served by a specific public transit operating organization or agency.
-
E.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
- 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_69a4948689d08190b3a4a3f388c02148 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bf41c5d08190b07adbdb24d35a76 |
completed | March 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69a4bb696a38819095845c84f0241287 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.