Triple
T33648621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edmund Ward |
E862028
|
entity |
| Predicate | publisherOfCharacter |
P117210
|
FINISHED |
| Object | Thomas the Tank Engine |
—
|
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: Thomas the Tank Engine | Statement: [Edmund Ward, publisherOfCharacter, Thomas the Tank Engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherOfCharacter Context triple: [Edmund Ward, publisherOfCharacter, Thomas the Tank Engine]
-
A.
publisherOfWorksFeaturingCharacter
chosen
Indicates that one entity is the publisher responsible for releasing works in which a given character appears.
-
B.
publisherOfSeries
Indicates that an entity serves as the publishing organization responsible for producing or distributing a particular series.
-
C.
publisherInUniverse
Indicates that a publisher operates, exists, or is recognized within a particular fictional or conceptual universe.
-
D.
publisherOfWorks
Indicates that one entity serves as the publisher responsible for issuing or distributing the works created by another entity.
-
E.
comicPublisher
Indicates that one entity is the publisher responsible for producing or distributing the comic associated with another 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff1c91bbac8190b84012dee1cb3b2c |
completed | May 9, 2026, 11:37 a.m. |
| PD | Predicate disambiguation | batch_69ff1c23ca508190bb5a435d765b7e53 |
completed | May 9, 2026, 11:36 a.m. |
Created at: May 1, 2026, 1:42 a.m.