Triple
T33379549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tin Woodman’s Castle |
E854732
|
entity |
| Predicate | hasInUniverseTitleHolder |
P1911
|
FINISHED |
| Object | Emperor of the Winkies |
—
|
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: Emperor of the Winkies | Statement: [Tin Woodman’s Castle, hasInUniverseTitleHolder, Emperor of the Winkies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInUniverseTitleHolder Context triple: [Tin Woodman’s Castle, hasInUniverseTitleHolder, Emperor of the Winkies]
-
A.
hasEponymousTitleHolder
Indicates that an entity has a title or position that is held by a person or figure after whom that title is named.
-
B.
hasTitleHolder
chosen
Indicates that one entity is the current or designated holder of a specific title, position, or honor associated with another entity.
-
C.
hasTitleHolderAward
Indicates that an entity holds or has been granted a specific title-related award.
-
D.
inUniverseTitle
Indicates that a work’s title is the one used within the fictional universe itself, as opposed to an external or real-world title.
-
E.
hasTitleHolderCategory
Indicates the category or classification assigned to the holder of a particular title.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ffe613c03481909f3043ec8bf0bed9 |
completed | May 10, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69ffe4a73fb4819091600725a443981a |
completed | May 10, 2026, 1:51 a.m. |
Created at: May 1, 2026, 1:35 a.m.