Triple
T2512574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supermarine Scimitar |
E52733
|
entity |
| Predicate | roleInService |
P268
|
FINISHED |
| Object | interim strike aircraft for Royal Navy |
—
|
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: interim strike aircraft for Royal Navy | Statement: [Supermarine Scimitar, roleInService, interim strike aircraft for Royal Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInService Context triple: [Supermarine Scimitar, roleInService, interim strike aircraft for Royal Navy]
-
A.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
B.
servedInRole
Indicates that one entity performed duties or held a position within a specified role or office in relation to another entity.
-
C.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
D.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
- 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_69ab4958e76481908a235377dd921c9e |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.