Triple
T37833835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book VII (Zanoni) |
E943279
|
entity |
| Predicate | hasMainWorkCharacter |
P97041
|
FINISHED |
| Object | Zanoni (character) |
E939704
|
NE 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: Zanoni (character) | Statement: [Book VII (Zanoni), hasMainWorkCharacter, Zanoni (character)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainWorkCharacter Context triple: [Book VII (Zanoni), hasMainWorkCharacter, Zanoni (character)]
-
A.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
B.
hasPrimaryCharacter
chosen
Indicates that an entity features another entity as its main or central character.
-
C.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
D.
hasMainProtagonistTrait
Indicates that the specified trait is a defining or primary characteristic of the main protagonist.
-
E.
hasMainThemeCharacter
Indicates that a work (such as a story, film, or game) features a specific character as its central or primary thematic focus.
- F. None of above.
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_69f76eea4c8c8190a335aed5955cf2db |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb834a988190aca7fc6a981f4fd2 |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:19 p.m.