Triple
T31492814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Horse and His Boy |
E803452
|
entity |
| Predicate | publicationOrderInSeries |
P54760
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [The Horse and His Boy, publicationOrderInSeries, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicationOrderInSeries Context triple: [The Horse and His Boy, publicationOrderInSeries, 5]
-
A.
opusPublicationOrder
Indicates the sequential order in which a creator’s works (opuses) are published relative to one another.
-
B.
publicationSeriesType
Indicates the specific kind or category of series to which a publication belongs (e.g., journal series, book series, report series).
-
C.
literarySeriesOrderByPublication
chosen
Indicates the position of a work within a literary series based on the chronological order in which the works were published.
-
D.
precedesInPublication
Indicates that one item is published or released before another in a temporal or sequential order.
-
E.
printedInSeries
Indicates that a work was published as part of a particular series or serial publication.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe744faca881908e11e90e0a35653f |
completed | May 8, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69fe734cbf7081909a552c5cf3b5ea59 |
completed | May 8, 2026, 11:35 p.m. |
Created at: April 30, 2026, 9:39 p.m.