Triple
T26630371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Pevensie |
E668473
|
entity |
| Predicate | doesNotReturnToNarniaAfter |
P162809
|
FINISHED |
| Object | Prince Caspian |
—
|
NE NERFINISHED |
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: Prince Caspian | Statement: [Peter Pevensie, doesNotReturnToNarniaAfter, Prince Caspian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotReturnToNarniaAfter Context triple: [Peter Pevensie, doesNotReturnToNarniaAfter, Prince Caspian]
-
A.
cannotDieInHumanSense
Indicates that the entity is not subject to death or mortality in the way humans experience or understand it.
-
B.
neverDestroyed
Indicates that the entity has not been destroyed at any point in time and remains intact or existent throughout the relevant period.
-
C.
notImmortal
Indicates that the entity does not possess immortality and is subject to death or an end to its existence.
-
D.
didNotLiveToSee
Indicates that one entity died before a particular event or state involving another entity occurred, and therefore never witnessed it.
-
E.
diesAtMomentOf
Indicates that one entity ceases to live precisely at the specific moment or time point associated with another entity or event.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f62e4168a48190b45268f922780da6 |
completed | May 2, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62d5268ac8190835dc7119353b840 |
completed | May 2, 2026, 4:58 p.m. |
Created at: April 27, 2026, 2:24 a.m.