Triple
T30808980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Emperor of India |
E784585
|
entity |
| Predicate | reasonForMissingJutland |
P189345
|
FINISHED |
| Object | under refit during Battle of Jutland |
—
|
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: under refit during Battle of Jutland | Statement: [HMS Emperor of India, reasonForMissingJutland, under refit during Battle of Jutland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForMissingJutland Context triple: [HMS Emperor of India, reasonForMissingJutland, under refit during Battle of Jutland]
-
A.
reasonForMissingFeature
Indicates the explanation or cause for why a particular feature is absent or not implemented.
-
B.
reasonForElimination
Indicates the specific cause or justification for why an entity was removed, disqualified, or excluded from consideration.
-
C.
reasonNotInForce
Indicates that a rule, law, or agreement is not currently valid or applicable due to a specified reason.
-
D.
abolishedReason
Indicates the reason or cause for which something (such as a law, practice, or institution) was abolished.
-
E.
reasonForScuttling
Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
- F. None of above. chosen
Provenance (4 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbbc48b75c8190bec27dd4b7de797f |
completed | May 6, 2026, 10:10 p.m. |
Created at: April 29, 2026, 8:43 p.m.