Triple
T31946589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chalice Dungeons |
E815665
|
entity |
| Predicate | progressionTiedTo |
P178351
|
FINISHED |
| Object | Pthumeru Chalice line |
—
|
NE NERFINISHED |
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: Pthumeru Chalice line | Statement: [Chalice Dungeons, progressionTiedTo, Pthumeru Chalice line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressionTiedTo Context triple: [Chalice Dungeons, progressionTiedTo, Pthumeru Chalice line]
-
A.
tiedTo
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
-
B.
progressedBy
Indicates that an activity, process, or state advances or moves forward as a result of the actions or influence of a specified agent or factor.
-
C.
hasProgressionSystem
Indicates that an entity includes or is associated with a structured system through which progress, advancement, or development can occur over time.
-
D.
continuesToward
Indicates that an entity maintains its movement or progression in the direction of a specified target or destination.
-
E.
tieInWith
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
- F. None of above. chosen
Provenance (4 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: May 1, 2026, 12:06 a.m.