Triple
T12594433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RMS Queen Elizabeth |
E300697
|
entity |
| Predicate | caughtFire |
P27153
|
FINISHED |
| Object | 1972-01 |
—
|
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: 1972-01 | Statement: [RMS Queen Elizabeth, caughtFire, 1972-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caughtFire Context triple: [RMS Queen Elizabeth, caughtFire, 1972-01]
-
A.
caughtBetween
Indicates being simultaneously subject to opposing forces, demands, or sides, unable to fully align with or escape either.
-
B.
fires
Indicates that an agent initiates the discharge or ignition of something, such as a weapon, engine, or explosive device, causing it to operate or go off.
-
C.
fireProblemSince
Indicates that a fire-related problem has been occurring or has been present since a specific point in time.
-
D.
notableFire
chosen
Indicates that a significant or historically important fire event is associated with the subject.
-
E.
secondaryFire
Indicates the use or activation of an alternate or secondary mode of firing in a weapon or tool, distinct from its primary fire action.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.