Triple
T29870699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider-Verse suit |
E758586
|
entity |
| Predicate | unlockable |
P168693
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Spider-Verse suit, unlockable, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockable Context triple: [Spider-Verse suit, unlockable, yes]
-
A.
unlockBehavior
Indicates that one entity enables access to or activates the behavior, functionality, or state of another entity.
-
B.
lock
Indicates that an entity secures or fastens another entity so that it cannot be opened, accessed, or changed without authorization.
-
C.
notAccessibleBy
Indicates that one entity cannot be reached, used, or obtained through another specified entity or means.
-
D.
lockedMeans
Indicates that one state, condition, or action guarantees or necessitates another, such that when the first is "locked in," the second must follow.
-
E.
unlocksUpgrade
Indicates that performing one action or meeting one condition enables access to a higher-level feature, capability, or version of something.
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f676c577fc819089d5842f5edc4148 |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 29, 2026, 5:53 p.m.