Triple
T37138678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonas Hollander |
E920042
|
entity |
| Predicate | characterArcLocation |
P201175
|
FINISHED |
| Object | Germany |
—
|
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: Germany | Statement: [Jonas Hollander, characterArcLocation, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterArcLocation Context triple: [Jonas Hollander, characterArcLocation, Germany]
-
A.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
B.
titleCharacterLocation
Indicates the location or setting associated with the main character referenced in the title.
-
C.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
D.
characterArcContinuation
Indicates that a character’s development or transformation in the narrative continues from a previous point or installment, maintaining coherence and progression in their storyline.
-
E.
linkedCharacterArc
Indicates that one character’s narrative development is directly connected to, influenced by, or dependent on another character’s arc.
- F. None of above. chosen
Provenance (4 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffcf46fd688190907fd1ceb499a8d1 |
completed | May 10, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69ffccde2a8c81908e055e74077dbd19 |
completed | May 10, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69ffcf4631cc8190aefa4b8f0b940b89 |
completed | May 10, 2026, 12:20 a.m. |
Created at: May 3, 2026, 4:15 p.m.