Triple
T11658700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nether |
E277070
|
entity |
| Predicate | hasUniqueResource |
P39874
|
FINISHED |
| Object | nether quartz |
—
|
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: nether quartz | Statement: [Nether, hasUniqueResource, nether quartz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUniqueResource Context triple: [Nether, hasUniqueResource, nether quartz]
-
A.
hasUniqueStatus
Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
-
B.
isUniqueTo
chosen
Indicates that a property, characteristic, or association belongs exclusively to a particular entity and is not shared with any other.
-
C.
isUniqueWithinSystem
Indicates that an entity exists only once and has no duplicates within the defined system or scope.
-
D.
hasResourceConstraint
Indicates that an entity is subject to a limitation or restriction on the resources it can use or access.
-
E.
hasKeyResource
Indicates that an entity possesses or depends on a critical resource necessary for its function, operation, or success.
- 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.