Triple
T13515121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McChord Field |
E322739
|
entity |
| Predicate | roleWithinJointBase |
P110072
|
FINISHED |
| Object | airfield component of Joint Base Lewis–McChord |
—
|
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: airfield component of Joint Base Lewis–McChord | Statement: [McChord Field, roleWithinJointBase, airfield component of Joint Base Lewis–McChord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleWithinJointBase Context triple: [McChord Field, roleWithinJointBase, airfield component of Joint Base Lewis–McChord]
-
A.
roleInCommandStructure
Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
-
B.
roleAtD.C.United
Indicates that an entity holds or held a specific role or position within the D.C. United soccer organization.
-
C.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
roleInMissions
Indicates the specific function, duty, or position an entity holds within one or more missions.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafa0ed508190b2855171b1945e84 |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaee128d88190b097be17fdd2f92b |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:44 p.m.