Triple
T38610319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Haunted |
E934458
|
entity |
| Predicate | hasTrilogyPart |
P113808
|
FINISHED |
| Object | Homecoming |
—
|
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: Homecoming | Statement: [The Haunted, hasTrilogyPart, Homecoming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrilogyPart Context triple: [The Haunted, hasTrilogyPart, Homecoming]
-
A.
hasTrilogy
Indicates that an entity is part of, or associated with, a specific trilogy within a larger set of works or narratives.
-
B.
hasPartInTrilogy
chosen
Indicates that an entity is one of the constituent parts (e.g., books, films, or episodes) that together form a specific trilogy.
-
C.
partOfTrilogy
Indicates that one work belongs to a set of three related works that together form a trilogy.
-
D.
hasSequelInTrilogy
Indicates that one work in a trilogy is followed by another work that serves as its sequel within that same three-part series.
-
E.
hasTrilogyCompanionWorkEnglish
Indicates that an English-language work is associated with another work as part of a trilogy companion relationship.
- 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_69f76eccd6d081909ccce171011739a1 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: May 3, 2026, 4:32 p.m.