Triple
T37665318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End stone bricks |
E937806
|
entity |
| Predicate | hasBlockIDJava |
P189182
|
FINISHED |
| Object | minecraft:end_stone_bricks |
—
|
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: minecraft:end_stone_bricks | Statement: [End stone bricks, hasBlockIDJava, minecraft:end_stone_bricks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBlockIDJava Context triple: [End stone bricks, hasBlockIDJava, minecraft:end_stone_bricks]
-
A.
hasBlock
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
hasUniqueBlock
Indicates that an entity is associated with exactly one distinct block, and no other entity shares that same block.
-
C.
hasBlockStatus
Indicates that one entity is currently blocked or restricted in its interaction or access relative to another entity.
-
D.
hasFeatureID
Indicates that an entity is associated with a specific feature identified by a unique ID.
-
E.
hasBridgeID
Indicates that a bridge is associated with a specific identifying code or number.
- 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_69f76ed6df7c8190b018e5baea716ceb |
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:18 p.m.