Triple
T38306073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dang Airport |
E1032347
|
entity |
| Predicate | hasAccessTransportationMode |
P37966
|
FINISHED |
| Object | road |
—
|
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: road | Statement: [Dang Airport, hasAccessTransportationMode, road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessTransportationMode Context triple: [Dang Airport, hasAccessTransportationMode, road]
-
A.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
B.
transportModeAccess
chosen
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
C.
hasPrimaryTransportationMode
Indicates the main or most frequently used mode of transportation associated with an entity.
-
D.
hasPublicTransitMode
Indicates that a location, route, or service is associated with or supports a specific mode of public transportation (e.g., bus, train, tram).
-
E.
hasTransportationAbove
Indicates that one entity provides or has transportation infrastructure or services located above another entity (e.g., elevated roads, railways, or transit lines).
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:30 p.m.