Triple
T12734843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Queen Elizabeth 2 |
E304335
|
entity |
| Predicate | reEngined |
P3155
|
FINISHED |
| Object | 1986–1987 |
—
|
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: 1986–1987 | Statement: [RMS Queen Elizabeth 2, reEngined, 1986–1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reEngined Context triple: [RMS Queen Elizabeth 2, reEngined, 1986–1987]
-
A.
remasteredVersion
Indicates that one entity is a newly produced, higher-quality audio or visual version of another original recording or release.
-
B.
refit
chosen
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
C.
reRelease
Indicates that an entity is released again, typically representing a subsequent or updated release following an earlier one.
-
D.
reimagines
Indicates that one entity creatively reconceives, interprets, or presents another in a significantly new or different way.
-
E.
rebuiltFor
Indicates that one entity has been reconstructed, renovated, or modified specifically to serve the needs, purposes, or use of another entity.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96403957c81909acdee7bdae71696 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.