Triple
T31542865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Magician’s Nephew |
E804793
|
entity |
| Predicate | positionInSeriesByInternalChronology |
P23880
|
FINISHED |
| Object | first |
—
|
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: first | Statement: [The Magician’s Nephew, positionInSeriesByInternalChronology, first]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInSeriesByInternalChronology Context triple: [The Magician’s Nephew, positionInSeriesByInternalChronology, first]
-
A.
positionHeldInSeries
Indicates the specific role or placement an entity occupies within an ordered sequence or series.
-
B.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
-
C.
chronologicalOrderInSeries
chosen
Indicates that one entity appears earlier or later than another within an ordered sequence or series.
-
D.
chronologyWithinSubseries
Indicates that one entity occurs in chronological order within the temporal sequence defined by a specific subseries.
-
E.
timeInSeries
Indicates that one temporal value occurs within the duration or sequence span defined by another in a series.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
Created at: April 30, 2026, 10:07 p.m.