Triple
T37664956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crying Obsidian |
E937799
|
entity |
| Predicate | isOpaqueCube |
P188642
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crying Obsidian, isOpaqueCube, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOpaqueCube Context triple: [Crying Obsidian, isOpaqueCube, true]
-
A.
isOpaque
Indicates that one entity does not allow light or visual information to pass through it, preventing clear or any visibility of what is behind or within it.
-
B.
isSolid
Indicates that an entity exists in a solid physical state, maintaining a fixed shape and volume under normal conditions.
-
C.
isTransparentTo
Indicates that one entity allows another entity (such as light, information, or influence) to pass through or be perceived without obstruction or concealment.
-
D.
numberOfVisibleCubiesOnStandardCube
Indicates the count of cubelets (small cube faces) that are visible on a standard cube from a given viewpoint or configuration.
-
E.
isFullBlock
chosen
Indicates that one entity completely occupies or blocks the available space or capacity of another entity, leaving no remaining room.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.