Triple
T18182834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 32 Squadron RAF |
E435333
|
entity |
| Predicate | aircraftRoleHistory |
P71776
|
FINISHED |
| Object | fighter aircraft |
—
|
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: fighter aircraft | Statement: [No. 32 Squadron RAF, aircraftRoleHistory, fighter aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftRoleHistory Context triple: [No. 32 Squadron RAF, aircraftRoleHistory, fighter aircraft]
-
A.
notableAircraftRole
Indicates that an aircraft is notably associated with performing a particular role or function.
-
B.
historicalAircraftOperated
Indicates that an entity previously operated a specific aircraft model during a past period, but no longer does so.
-
C.
aircraftRoleOperated
chosen
Indicates that an entity operates or has operated in a specified role or function within the context of aircraft operations.
-
D.
aircraftRoleDesigned
Indicates that an aircraft was specifically designed to fulfill a particular operational role or function.
-
E.
aircraftRoleSupported
Indicates that a given role or function is supported or enabled for a particular aircraft.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffc432c8190af53da5256dc476c |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.