Triple
T5102087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stockholm |
E115002
|
entity |
| Predicate | hasCharacterDevelopment |
P20798
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Stockholm, hasCharacterDevelopment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterDevelopment Context triple: [Stockholm, hasCharacterDevelopment, yes]
-
A.
characterArc
chosen
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
B.
developmentCharacter
Indicates a relationship where one entity contributes to or influences the growth, formation, or evolution of another entity’s characteristics or qualities.
-
C.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
narrativeCharacter
Indicates that one entity functions as a character within the narrative or story associated with another 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7584ed408190a6d1086588f24faa |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.