Triple
T33240310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wingfoot |
E850943
|
entity |
| Predicate | inUniverseTitleOf |
P113153
|
FINISHED |
| Object | Heir of Isildur |
—
|
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: Heir of Isildur | Statement: [Wingfoot, inUniverseTitleOf, Heir of Isildur]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseTitleOf Context triple: [Wingfoot, inUniverseTitleOf, Heir of Isildur]
-
A.
inUniverseTitle
chosen
Indicates that a work’s title is the one used within the fictional universe itself, as opposed to an external or real-world title.
-
B.
inUniverseSongTitle
Indicates that a song’s title exists within the fictional universe of a work (e.g., a show, movie, or game) rather than only as a real-world track name.
-
C.
inUniverseStar
Indicates that a star exists or is located within a particular fictional or defined universe.
-
D.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
E.
inUniverseType
Indicates that one entity exists within, or is categorized as belonging to, a particular fictional or conceptual universe type defined by the other 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_69f34962386c81909ddc3bf9e18ddeb8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:31 a.m.