Triple
T36388159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Tyne |
E896254
|
entity |
| Predicate | usedInNavalVessel |
P88658
|
FINISHED |
| Object | Royal Navy Type 42 destroyer |
—
|
NE NERFINISHED |
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: Royal Navy Type 42 destroyer | Statement: [Rolls-Royce Tyne, usedInNavalVessel, Royal Navy Type 42 destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInNavalVessel Context triple: [Rolls-Royce Tyne, usedInNavalVessel, Royal Navy Type 42 destroyer]
-
A.
usedInNavy
chosen
Indicates that something is or was employed, operated, or otherwise utilized by a navy or naval forces.
-
B.
usedForShips
Indicates that something is designed, intended, or suitable to be used for ships or ship-related purposes.
-
C.
usedInMaritimeNavigation
Indicates that something is employed as a tool, aid, or reference in the practice of maritime navigation.
-
D.
usedOnNuclearPoweredVessel
Indicates that something is employed or operated aboard a vessel that is powered by nuclear energy.
-
E.
hasNavalComponent
Indicates that something includes, involves, or is associated with a naval or maritime element as part of its composition or structure.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: May 3, 2026, 4:10 p.m.