Triple
T11659871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deep Dark |
E277094
|
entity |
| Predicate | containsBlock |
P20311
|
FINISHED |
| Object | sculk catalyst |
—
|
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: sculk catalyst | Statement: [Deep Dark, containsBlock, sculk catalyst]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBlock Context triple: [Deep Dark, containsBlock, sculk catalyst]
-
A.
hasBlock
chosen
Indicates that one entity possesses, contains, or is associated with a specific block or blocking element in relation to another entity.
-
B.
belongsToBlock
Indicates that something is a member or component of a specific block or grouping.
-
C.
occupiesBlock
Indicates that one entity is physically positioned within or taking up space in a specified block or bounded area.
-
D.
hasBlockUnicode
Indicates that one entity possesses or is associated with a specific Unicode block related to another entity.
-
E.
relatedBlock
Indicates that one block is associated with or connected to another block in some relevant way.
- 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_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.