Triple
T37665303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End stone bricks |
E937806
|
entity |
| Predicate | blockSoundType |
P84027
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [End stone bricks, blockSoundType, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockSoundType Context triple: [End stone bricks, blockSoundType, stone]
-
A.
noteBlockSound
Indicates that a note block produces or is associated with a specific sound.
-
B.
soundMechanism
Indicates a relationship where one entity produces, transmits, or enables the production of sound for another entity or context.
-
C.
soundboardType
Indicates the specific category or configuration of a soundboard associated with an entity.
-
D.
soundEffects
Indicates that one entity produces, contains, or is associated with sound effects used to accompany or enhance another entity.
-
E.
soundCategory
chosen
Indicates the classification relationship where a sound is assigned to a particular category or type of sound.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.