Triple
T29362649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theed Royal Hangar |
E744630
|
entity |
| Predicate | hangarType |
P166681
|
FINISHED |
| Object | enclosed hangar complex |
—
|
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: enclosed hangar complex | Statement: [Theed Royal Hangar, hangarType, enclosed hangar complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hangarType Context triple: [Theed Royal Hangar, hangarType, enclosed hangar complex]
-
A.
hasHangars
Indicates that one entity possesses or contains hangars used for housing aircraft or similar vehicles.
-
B.
hangarComplement
Indicates that one entity serves as the hangar-based complement or support unit for another, typically housing, servicing, or supporting it within a hangar facility.
-
C.
hasHangarCount
Indicates the number of hangars associated with or contained by an entity.
-
D.
heliportType
Indicates the specific classification or category of a heliport based on its design, function, or operational characteristics.
-
E.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
- F. None of above. chosen
Provenance (4 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669894f608190941fed17608d9c2e |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69f661b47d088190934f63884a203261 |
completed | May 2, 2026, 8:42 p.m. |
Created at: April 28, 2026, 2:19 p.m.