Triple
T22150456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bamyan Airport |
E547397
|
entity |
| Predicate | hasTerminalInfrastructure |
P53208
|
FINISHED |
| Object | basic facilities |
—
|
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: basic facilities | Statement: [Bamyan Airport, hasTerminalInfrastructure, basic facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalInfrastructure Context triple: [Bamyan Airport, hasTerminalInfrastructure, basic facilities]
-
A.
hasTerminalFacility
chosen
Indicates that an entity possesses or includes a terminal facility used as an endpoint for transport, communication, or related operations.
-
B.
hasAccessInfrastructure
Indicates that an entity is equipped with or connected to the physical or technical infrastructure necessary to access a particular service, resource, or network.
-
C.
hasInfrastructureAbove
Indicates that one entity’s infrastructure is physically located above or over another entity.
-
D.
hasCommercialInfrastructure
Indicates that an entity possesses or is equipped with facilities, systems, or structures that support commercial or business activities.
-
E.
hasInfrastructureAlong
Indicates that infrastructure is present or extends along the length or course of another entity (such as a route, boundary, or geographic feature).
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f37dac8190a7cecb12f4271515 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:33 p.m.