Triple
T23775016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Redemption of the Beast |
E587646
|
entity |
| Predicate | hasUnauthorizedStatus |
P49355
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Redemption of the Beast, hasUnauthorizedStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnauthorizedStatus Context triple: [Redemption of the Beast, hasUnauthorizedStatus, true]
-
A.
hasAuthorityStatus
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
-
B.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
C.
notAuthorizedFor
chosen
Indicates that an entity lacks the required permission or authority to perform a specific action or access a particular resource.
-
D.
hasNoAccess
Indicates that an entity is denied or lacks permission to access another entity, resource, or location.
-
E.
hasUniqueStatus
Indicates that an entity possesses a status or condition that is distinct and not shared with any other entity in the given context.
- 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1c46a19688190aa91f1f10ba5c4ee |
completed | April 29, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69f155f79e34819080f9ddb972b34deb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:16 p.m.