Triple
T890030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sopwith Camel |
E19217
|
entity |
| Predicate | usedInRole |
P11687
|
FINISHED |
| Object | home defence 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: home defence fighter | Statement: [Sopwith Camel, usedInRole, home defence fighter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRole Context triple: [Sopwith Camel, usedInRole, home defence fighter]
-
A.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
B.
servesRole
chosen
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
C.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
- 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0086a081908c47c285896a1f3c |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.