Triple
T38619202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swift F.7 |
E936820
|
entity |
| Predicate | aircraftIntendedUse |
P2860
|
FINISHED |
| Object | day fighter |
—
|
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: day fighter | Statement: [Swift F.7, aircraftIntendedUse, day fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftIntendedUse Context triple: [Swift F.7, aircraftIntendedUse, day fighter]
-
A.
aircraftRoleDesignedFor
Indicates that an aircraft is specifically designed or intended to perform a particular role or function.
-
B.
aircraftRoleOfDesignatedAircraft
Indicates that an aircraft has the specified operational role or function as a designated aircraft within a particular context or mission.
-
C.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
D.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
E.
aircraftRoleSpecialization
Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:32 p.m.