Triple
T25808039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gowen Field Air National Guard Base |
E650025
|
entity |
| Predicate | hasPrimaryUnit |
P26710
|
FINISHED |
| Object | 124th Fighter Wing |
—
|
NE NERFINISHED |
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: 124th Fighter Wing | Statement: [Gowen Field Air National Guard Base, hasPrimaryUnit, 124th Fighter Wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryUnit Context triple: [Gowen Field Air National Guard Base, hasPrimaryUnit, 124th Fighter Wing]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
primaryUnit
chosen
Indicates that one entity serves as the main or principal unit associated with another entity, typically among multiple possible units.
-
C.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
D.
hasPrimaryConstituent
Indicates that one entity serves as the main or principal component, ingredient, or element of another entity.
-
E.
hasUnitIn
Indicates that one entity is contained or measured within another as a unit, specifying a unit-of-measure or component relationship.
- 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_69e7ab35d264819095367f7e80c983ff |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 22, 2026, 7:06 a.m.