Triple
T9107175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amaala |
E218505
|
entity |
| Predicate | infrastructureComponent |
P19374
|
FINISHED |
| Object | airfield |
—
|
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: airfield | Statement: [Amaala, infrastructureComponent, airfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureComponent Context triple: [Amaala, infrastructureComponent, airfield]
-
A.
isPartOfInfrastructure
chosen
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
B.
parallelInfrastructure
Indicates that two or more infrastructure elements are arranged or operate in parallel to each other, typically serving similar functions simultaneously.
-
C.
relatedInfrastructure
Indicates that one piece of infrastructure is connected, associated, or functionally related to another infrastructure element.
-
D.
infrastructureManager
Indicates a relationship where one entity is responsible for overseeing, maintaining, or administering the infrastructure of another entity or system.
-
E.
infrastructureRole
Indicates that one entity serves a specific infrastructural function or capacity in relation to another entity.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca573da0081909f4afcdb3ac99c53 |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.