Triple
T9219181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airborne Museum |
E221315
|
entity |
| Predicate | focusesOnMilitaryUnitType |
P6154
|
FINISHED |
| Object | paratroopers |
—
|
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: paratroopers | Statement: [Airborne Museum, focusesOnMilitaryUnitType, paratroopers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnMilitaryUnitType Context triple: [Airborne Museum, focusesOnMilitaryUnitType, paratroopers]
-
A.
focusesOnMilitaryUnit
Indicates that an entity’s attention, activity, or content is directed primarily toward a specific military unit.
-
B.
militaryUnitOf
Indicates that one entity is a military unit that belongs to, is part of, or is under the command or organizational structure of another entity.
-
C.
portraysMilitaryUnit
Indicates that one entity visually or narratively represents, depicts, or shows a specific military unit.
-
D.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
E.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
- 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_69ca83eae42c8190a0ea9e040710a277 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda730f688190b64b2cc8c4898ac3 |
completed | April 1, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:28 p.m.