Triple
T17222183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 209 Squadron RAF |
E418011
|
entity |
| Predicate | operationalRoleWWI |
P43732
|
FINISHED |
| Object | fighter and reconnaissance |
—
|
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 and reconnaissance | Statement: [No. 209 Squadron RAF, operationalRoleWWI, fighter and reconnaissance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationalRoleWWI Context triple: [No. 209 Squadron RAF, operationalRoleWWI, fighter and reconnaissance]
-
A.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
roleInWorldWarI
chosen
Indicates the specific function, position, or involvement an entity had during World War I.
-
C.
aircraftRoleOperated
Indicates that an entity operates or has operated in a specified role or function within the context of aircraft operations.
-
D.
preWarRole
Indicates the role, position, or function an entity held before the onset of a specified war or conflict.
-
E.
postWWIIRole
Indicates the role, position, or function an entity assumed or performed in the period following World War II.
- 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_69d886d779488190b131369541c04e7d |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dde78f881908b03105fa0298ae2 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3831e354881908c5505ffd15c84e9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:38 a.m.