Triple
T36122984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Young and Prodigious T.S. Spivet |
E1044794
|
entity |
| Predicate | titleCharacterFullName |
P81917
|
FINISHED |
| Object | Tecumseh Sparrow Spivet |
—
|
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: Tecumseh Sparrow Spivet | Statement: [The Young and Prodigious T.S. Spivet, titleCharacterFullName, Tecumseh Sparrow Spivet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleCharacterFullName Context triple: [The Young and Prodigious T.S. Spivet, titleCharacterFullName, Tecumseh Sparrow Spivet]
-
A.
titleCharacterString
Indicates that one entity is the textual string representing the title associated with another entity.
-
B.
characterFullName
chosen
Indicates that the predicate specifies the complete, formal name of a character.
-
C.
titleCharacterRealName
Indicates that a character known by a title or alias has the specified real (personal) name.
-
D.
characterTitle
Indicates that a character holds or is associated with a specific title, rank, or formal designation.
-
E.
titleCharacterNamedAfter
Indicates that a work’s title character is named after, or shares their name with, another specific entity.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9d9cb4f8819083682be3c483b599 |
completed | May 9, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69ff9c38bf9c8190bbb85b32f3ae3d2e |
completed | May 9, 2026, 8:42 p.m. |
Created at: May 3, 2026, 4:08 p.m.