Triple
T37662700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Swiftness |
E937750
|
entity |
| Predicate | requiresBlock |
P100
|
FINISHED |
| Object | Brewing Stand |
—
|
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: Brewing Stand | Statement: [Potion of Swiftness, requiresBlock, Brewing Stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBlock Context triple: [Potion of Swiftness, requiresBlock, Brewing Stand]
-
A.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
B.
requiresCall
Indicates that one entity must initiate or receive a phone call or similar direct voice communication with another entity as a necessary condition for some action or state.
-
C.
requiresPass
Indicates that access to or participation in something is conditional on possessing a valid pass.
-
D.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_6a00818b20a881909fbf3bb33dcf7029 |
completed | May 10, 2026, 1 p.m. |
| PD | Predicate disambiguation | batch_6a0080f76f588190a933238861243d1a |
completed | May 10, 2026, 12:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.