Triple
T4752677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Air Force |
E105513
|
entity |
| Predicate | 201st Fighter SquadronRole |
P9463
|
FINISHED |
| Object | expeditionary fighter unit in World War II |
—
|
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: expeditionary fighter unit in World War II | Statement: [Mexican Air Force, 201st Fighter SquadronRole, expeditionary fighter unit in World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 201st Fighter SquadronRole Context triple: [Mexican Air Force, 201st Fighter SquadronRole, expeditionary fighter unit in World War II]
-
A.
squadron
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
B.
fighter1
Indicates that the subject is the first participant or primary combatant in a fight or competitive physical confrontation.
-
C.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
primaryAircraftRole
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
E.
squadronCode
Indicates the identifying code assigned to a military or aviation squadron that denotes its unit designation.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64e5fba88190b1f28d1b0eed3f8e |
completed | March 20, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69bd6223defc8190823665a6592c1154 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.