Triple
T37661798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nether Star |
E937733
|
entity |
| Predicate | usedInMechanic |
P25490
|
FINISHED |
| Object | beacon pyramid effects |
—
|
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: beacon pyramid effects | Statement: [Nether Star, usedInMechanic, beacon pyramid effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMechanic Context triple: [Nether Star, usedInMechanic, beacon pyramid effects]
-
A.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
usedOnPart
Indicates that something is applied to, operates on, or is intended for use with a specific part of a larger object or system.
-
C.
mecanismo
Indicates a mechanism or means by which one entity brings about, enables, or explains the effect, function, or outcome in another entity.
-
D.
usedInPartOf
Indicates that something is utilized or plays a functional role within a specific component or subpart of a larger whole.
-
E.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
- 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_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4:18 p.m.