Triple
T34622757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairey IIIF |
E889050
|
entity |
| Predicate | operatorRoleRAF |
P84579
|
FINISHED |
| Object | general-purpose landplane |
—
|
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: general-purpose landplane | Statement: [Fairey IIIF, operatorRoleRAF, general-purpose landplane]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorRoleRAF Context triple: [Fairey IIIF, operatorRoleRAF, general-purpose landplane]
-
A.
RAFRole
chosen
Indicates that an entity holds or is assigned a specific role within the Royal Air Force.
-
B.
operatorRoleUSAAF
Indicates that an entity served in an operator role within the United States Army Air Forces (USAAF) in relation to another entity or activity.
-
C.
RANRole
Indicates that one entity holds or is assigned a specific role within a Royal Australian Navy (RAN) context in relation to another entity.
-
D.
FLETCRole
Indicates that an entity serves in a specific role or capacity within the FLETC (Federal Law Enforcement Training Centers) context.
-
E.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00c9ddd62881909859a36b114a4132 |
completed | May 10, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_6a00c939b88881909d5353db4265e572 |
completed | May 10, 2026, 6:06 p.m. |
Created at: May 1, 2026, 2:04 a.m.