Triple
T14807656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMS Blücher |
E348078
|
entity |
| Predicate | outclassedBy |
P29489
|
FINISHED |
| Object | British battlecruisers |
—
|
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: British battlecruisers | Statement: [SMS Blücher, outclassedBy, British battlecruisers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outclassedBy Context triple: [SMS Blücher, outclassedBy, British battlecruisers]
-
A.
defeatedBy
Indicates that one entity has been beaten, overcome, or conquered by another in a contest, conflict, or competition.
-
B.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
C.
overshadowedBy
chosen
Indicates that one entity’s importance, visibility, or impact is diminished because another entity is more prominent or dominant.
-
D.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
E.
isEliminatedPrimarilyBy
Indicates that one entity serves as the main means or pathway by which another entity is removed, cleared, or disposed of.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf33b6a08190ab6a4cfeda2cc09c |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:42 a.m.