Triple
T348307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supermarine |
E6987
|
entity |
| Predicate | spitfireRole |
P2860
|
FINISHED |
| Object | single-seat 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: single-seat fighter | Statement: [Supermarine, spitfireRole, single-seat fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spitfireRole Context triple: [Supermarine, spitfireRole, single-seat fighter]
-
A.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
B.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
C.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
primaryBritishFighterAircraft
Indicates that an aircraft serves as the main or most important fighter aircraft used by British military forces.
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.