Triple
T33811969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toby the Tram Engine |
E866559
|
entity |
| Predicate | introducedInBookNumber |
P104268
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Toby the Tram Engine, introducedInBookNumber, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInBookNumber Context triple: [Toby the Tram Engine, introducedInBookNumber, 7]
-
A.
appearsInBookNumber
chosen
Indicates that an entity is featured or mentioned in a specific book identified by its number within a series or collection.
-
B.
firstTaughtInBook
Indicates that a concept, method, or topic is initially introduced or taught within a specific book.
-
C.
editionNumber
Indicates the specific sequential number assigned to an edition of a work within its series of published versions.
-
D.
sourceBookVolume
Indicates the specific volume of a book from which the referenced material or information originates.
-
E.
introducedInTitle
Indicates that something (such as a concept, character, or term) is first presented or brought into use within a specified title (e.g., a book, article, or work).
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: May 1, 2026, 1:46 a.m.