Triple
T33235490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Soldier (plate) |
E850815
|
entity |
| Predicate | hasBlockCutter |
P75448
|
FINISHED |
| Object | Hans Lützelburger |
—
|
NE NERFINISHED |
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: Hans Lützelburger | Statement: [The Soldier (plate), hasBlockCutter, Hans Lützelburger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockCutter Context triple: [The Soldier (plate), hasBlockCutter, Hans Lützelburger]
-
A.
canBreakBlocks
Indicates that an entity has the ability to destroy or remove blocks within the environment.
-
B.
cutter
chosen
Indicates that an entity is used to cut or divide another entity.
-
C.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
D.
canPickUpBlocks
Indicates that an entity has the ability to lift and carry blocks.
-
E.
isCutInto
Indicates that one entity is divided or separated into pieces or segments that become the other entity.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.