Triple
T36044013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mia Hall |
E1042616
|
entity |
| Predicate | bookSequelAppearance |
P48180
|
FINISHED |
| Object | Where She Went |
—
|
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: Where She Went | Statement: [Mia Hall, bookSequelAppearance, Where She Went]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookSequelAppearance Context triple: [Mia Hall, bookSequelAppearance, Where She Went]
-
A.
sequelAppearsIn
Indicates that a sequel (such as a follow-up work or installment) is featured, shown, or occurs within a specified context or medium.
-
B.
hasSequelAppearance
chosen
Indicates that an entity appears again in a subsequent installment or sequel of a work.
-
C.
hasSequelDepiction
Indicates that one depiction of something is followed by another depiction that continues its story or sequence.
-
D.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
E.
hasSequelInCanon
Indicates that a work has a subsequent work that continues its story within the officially recognized continuity.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.