Triple
T16119316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halberstadt D.II |
E391090
|
entity |
| Predicate | airServiceType |
P121552
|
FINISHED |
| Object | army air service |
—
|
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: army air service | Statement: [Halberstadt D.II, airServiceType, army air service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airServiceType Context triple: [Halberstadt D.II, airServiceType, army air service]
-
A.
airService
Indicates that an air transportation service (such as flights or air routes) is provided or operates between the related entities.
-
B.
airGroupType
Indicates the classification or category of an air group based on its role, composition, or operational function.
-
C.
airSupplyMethod
Indicates the method or system by which air is provided or delivered to a space, device, or process.
-
D.
airWingType
Indicates the classification or category of an air wing associated with an entity.
-
E.
airGroup
Indicates a relationship where entities are grouped or organized together based on their association with air or aerial operations.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016d527c8190928e73661b18a914 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e183b9d3f08190953ada68f4272996 |
completed | April 17, 2026, 12:50 a.m. |
Created at: April 10, 2026, 5 a.m.