Triple
T25707362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery of the Vanished Prince |
E644628
|
entity |
| Predicate | literarySeriesLeadCharacter |
P75850
|
FINISHED |
| Object | Fatty |
—
|
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: Fatty | Statement: [The Mystery of the Vanished Prince, literarySeriesLeadCharacter, Fatty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literarySeriesLeadCharacter Context triple: [The Mystery of the Vanished Prince, literarySeriesLeadCharacter, Fatty]
-
A.
literarySeriesCharacter
chosen
Indicates that a character appears in, is part of, or is associated with a particular literary series.
-
B.
literarySeries
Indicates that one work is part of, or belongs to, a larger literary series that connects multiple related works.
-
C.
literarySeriesDebut
Indicates the work in which a literary series first appeared or was initially introduced.
-
D.
literaryCharacterModeledAs
Indicates that one literary character is created or portrayed based on the traits, life, or persona of another real or fictional individual.
-
E.
storyCharacterizedAs
Indicates that a story is described, portrayed, or defined as having a particular quality, style, or attribute.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6456608190b94e7c2e2c2a4824 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 21, 2026, 9:06 p.m.