Triple
T37471266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Twisting Corridors |
E931157
|
entity |
| Predicate | doesNotReward |
P72170
|
FINISHED |
| Object | player power |
—
|
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: player power | Statement: [Twisting Corridors, doesNotReward, player power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotReward Context triple: [Twisting Corridors, doesNotReward, player power]
-
A.
notAwardedWhen
chosen
Indicates that one entity is not granted, conferred, or given in the circumstances or conditions specified by another entity or event.
-
B.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
doesNotBan
Indicates that one entity allows or permits another entity or action by explicitly not prohibiting it.
-
D.
notAwardedFor
Indicates that a particular award, prize, or honor was explicitly not given in recognition of a specified work, achievement, or entity.
-
E.
doesNotClaim
Indicates that an entity explicitly refrains from asserting, alleging, or taking ownership of a particular statement, right, or responsibility.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.