Triple
T38061379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eve of Destruction |
E950347
|
entity |
| Predicate | unlocksAfter |
P168000
|
FINISHED |
| Object | Rite of Passage completion |
—
|
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: Rite of Passage completion | Statement: [Eve of Destruction, unlocksAfter, Rite of Passage completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlocksAfter Context triple: [Eve of Destruction, unlocksAfter, Rite of Passage completion]
-
A.
canUnlock
Indicates that one entity has the ability or permission to unlock another entity.
-
B.
unlocksUpgrade
chosen
Indicates that performing one action or meeting one condition enables access to a higher-level feature, capability, or version of something.
-
C.
unlocksViaNormalExit
Indicates that something becomes unlocked when a standard or regular exit is used.
-
D.
unlockable
Indicates that an entity can be opened or made accessible, typically by using a key, code, or other authorized method.
-
E.
unlockType
Indicates the method or condition by which access to something is unlocked or made available.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.