Triple
T38495336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warfield Air National Guard Base |
E919675
|
entity |
| Predicate | primaryFlyingUnit |
P186678
|
FINISHED |
| Object | 104th Fighter Squadron |
E916746
|
NE 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: 104th Fighter Squadron | Statement: [Warfield Air National Guard Base, primaryFlyingUnit, 104th Fighter Squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFlyingUnit Context triple: [Warfield Air National Guard Base, primaryFlyingUnit, 104th Fighter Squadron]
-
A.
primaryUnitAircraft
Indicates that an aircraft serves as the main or principal aircraft assigned to a particular unit.
-
B.
primaryUSAAFUnit
Indicates that one entity is the main or principal United States Army Air Forces unit associated with, responsible for, or assigned to the other entity.
-
C.
hasFlyingUnit
chosen
Indicates that an entity possesses or is associated with a unit capable of flight.
-
D.
aerialUnit
Indicates that the related entity functions as or is classified as an aerial unit, typically operating or acting in the air rather than on the ground or sea.
-
E.
alliedAirUnit
Indicates that an air unit is friendly or allied to the reference side or force.
- F. None of above.
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_69f76e9ddd4481908f8c04439d848f9d |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41d6512f70819084dc118d54048be2 |
completed | June 29, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.