Triple
T15383824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Question Block |
E367868
|
entity |
| Predicate | visualChangeAfterHit |
P38840
|
FINISHED |
| Object | turns into a used block |
—
|
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: turns into a used block | Statement: [Question Block, visualChangeAfterHit, turns into a used block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualChangeAfterHit Context triple: [Question Block, visualChangeAfterHit, turns into a used block]
-
A.
surfaceChange
chosen
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
-
B.
visibilityCycle
Indicates a recurring pattern in which something alternates between being visible and not visible over time.
-
C.
visibleAfter
Indicates that one entity becomes perceptible or can be seen only after another specified event, time, or condition has occurred.
-
D.
visualEffect
Indicates that one entity produces, modifies, or is associated with a particular visual effect on another entity or within a scene.
-
E.
viewOnRevelation
Indicates the stance or interpretation an entity holds regarding the nature, source, or authority of divine revelation.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.