Triple
T38589131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lower Spire |
E932412
|
entity |
| Predicate | unlocksAccessTo |
P191455
|
FINISHED |
| Object | The Plagueworks |
—
|
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: The Plagueworks | Statement: [The Lower Spire, unlocksAccessTo, The Plagueworks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlocksAccessTo Context triple: [The Lower Spire, unlocksAccessTo, The Plagueworks]
-
A.
canUnlock
Indicates that one entity has the ability or permission to unlock another entity.
-
B.
unlocksUpgrade
Indicates that performing one action or meeting one condition enables access to a higher-level feature, capability, or version of something.
-
C.
assumesAccessTo
Indicates that one entity presupposes or takes for granted that it has access to another entity, resource, or piece of information.
-
D.
unlockType
Indicates the method or condition by which access to something is unlocked or made available.
-
E.
releaseObtainedBy
Indicates that a particular release results from, or is produced through, a specified obtaining or acquisition process.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:32 p.m.