Triple
T26630359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Pevensie |
E668473
|
entity |
| Predicate | crownCoRuler |
P161072
|
FINISHED |
| Object | Lucy Pevensie |
—
|
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: Lucy Pevensie | Statement: [Peter Pevensie, crownCoRuler, Lucy Pevensie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crownCoRuler Context triple: [Peter Pevensie, crownCoRuler, Lucy Pevensie]
-
A.
crownCoRuler
chosen
Indicates a relationship where two or more individuals are jointly crowned and officially recognized as co-rulers of the same realm or title.
-
B.
monarchCrowned
Indicates that an individual has been formally installed as a monarch through a coronation ceremony.
-
C.
crownedBy
Indicates that an entity is formally invested with a rank, title, or authority through a crowning ceremony performed by another entity.
-
D.
crownDepicted
Indicates that one entity visually represents or shows a crown associated with another entity.
-
E.
crownedAs
Indicates that one entity is formally invested with a royal or ceremonial title or position by another entity or authority.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 2:24 a.m.