Triple
T37550986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death Knight |
E933588
|
entity |
| Predicate | canTankInSpec |
P189157
|
FINISHED |
| Object | Blood |
—
|
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: Blood | Statement: [Death Knight, canTankInSpec, Blood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canTankInSpec Context triple: [Death Knight, canTankInSpec, Blood]
-
A.
hasTankType
Indicates that an entity is associated with, or classified by, a specific type or category of tank.
-
B.
hasTank
Indicates that an entity possesses, is equipped with, or contains a tank (such as a storage tank, fuel tank, or similar vessel).
-
C.
mainTankCapacity
Indicates the maximum volume of fuel or liquid that the primary tank is designed to hold.
-
D.
hasTankerClass
Indicates that an entity is associated with, or belongs to, a particular class or category of tanker.
-
E.
hasCentralTank
Indicates that an entity possesses or is equipped with a primary central tank as a key component or feature.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69fbb9e69b7481909beaf8264d87c5e5 |
completed | May 6, 2026, 10 p.m. |
Created at: May 3, 2026, 4:17 p.m.