Triple
T7025077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defiant Mk I |
E162922
|
entity |
| Predicate | initialOperationalRole |
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: [Defiant Mk I, initialOperationalRole, day fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialOperationalRole Context triple: [Defiant Mk I, initialOperationalRole, day fighter]
-
A.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
B.
firstOperationalTarget
Indicates that an entity is designated as the initial or primary target to be acted upon or engaged in an operation.
-
C.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
D.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
E.
aircraftRoleOperated
Indicates that an entity operates or has operated in a specified role or function within the context of aircraft operations.
- 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_69c6885b26248190a857541e3d10e299 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e5ecd4488190bf19e42de55da98b |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b8118481909d76eb6616160e80 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.