Triple
T30519286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kidal Airport |
E776648
|
entity |
| Predicate | infrastructureScale |
P62107
|
FINISHED |
| Object | small regional airport |
—
|
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: small regional airport | Statement: [Kidal Airport, infrastructureScale, small regional airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureScale Context triple: [Kidal Airport, infrastructureScale, small regional airport]
-
A.
infrastructureLevel
Indicates the degree or quality of infrastructure present or provided in relation to an entity or location.
-
B.
typicalInfrastructure
Indicates that something is part of the standard or commonly expected infrastructure associated with a given context or entity.
-
C.
hasInfrastructureScale
chosen
Indicates the relative size, capacity, or extent of infrastructure associated with or supporting an entity.
-
D.
infrastructureFocusArea
Indicates the specific aspect or domain of infrastructure that an entity, project, or activity is primarily concerned with or directed toward.
-
E.
isPartOfInfrastructureType
Indicates that something belongs to, or is categorized under, a specific type of infrastructure.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6880930e4819084605c33854cf72a |
completed | May 2, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:17 p.m.