Triple
T11658684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nether |
E277070
|
entity |
| Predicate | hasPrimaryBlock |
P20311
|
FINISHED |
| Object | netherrack |
—
|
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: netherrack | Statement: [Nether, hasPrimaryBlock, netherrack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryBlock Context triple: [Nether, hasPrimaryBlock, netherrack]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasBlock
chosen
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
C.
hasPrimaryCode
Indicates that an entity is associated with its main or most important identifying code among potentially multiple codes.
-
D.
hasPrimaryFeature
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
E.
hasPrimaryAnchor
Indicates that one entity serves as the main or principal anchor or reference point for another 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.