Triple
T17258840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinvat Bridge |
E418954
|
entity |
| Predicate | fateOfWicked |
P23287
|
FINISHED |
| Object | bridge becomes narrow and difficult to cross |
—
|
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: bridge becomes narrow and difficult to cross | Statement: [Chinvat Bridge, fateOfWicked, bridge becomes narrow and difficult to cross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfWicked Context triple: [Chinvat Bridge, fateOfWicked, bridge becomes narrow and difficult to cross]
-
A.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
B.
fateInSequel
Indicates that the outcome or destiny of an entity is revealed or occurs in a subsequent work, installment, or sequel.
-
C.
fateInLegend
Indicates the ultimate outcome or destiny attributed to an entity within a particular legend or mythic narrative.
-
D.
fateInBooks
Indicates that a character’s destiny, outcome, or predetermined path is described or revealed within written works or books.
-
E.
afterlifeFate
chosen
Indicates the outcome or condition an entity experiences in the afterlife as a result of its life or actions.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e6ea7588190a94d222504a8cef5 |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.