Triple
T31593896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highball |
E806170
|
entity |
| Predicate | notableIntendedTarget |
P207468
|
FINISHED |
| Object | German battleship Tirpitz |
E144915
|
NE 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: German battleship Tirpitz | Statement: [Highball, notableIntendedTarget, German battleship Tirpitz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableIntendedTarget Context triple: [Highball, notableIntendedTarget, German battleship Tirpitz]
-
A.
notableTarget
Indicates that the subject is particularly significant, prominent, or noteworthy with respect to the specified target.
-
B.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
C.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
D.
intendedTargets
Indicates that an action, message, or object is specifically directed toward or meant to affect particular target entities.
-
E.
aimedAtBy
Indicates that one entity serves as the target or goal toward which another entity directs an action, intention, or focus.
- F. None of above. chosen
Provenance (5 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b56550d70819088b6012b38610d67 |
completed | June 12, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 30, 2026, 10:29 p.m.