Triple
T34933613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victor |
E1007507
|
entity |
| Predicate | primaryViewpointCharacterIn |
P9202
|
FINISHED |
| Object | High Seas |
E307826
|
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: High Seas | Statement: [Victor, primaryViewpointCharacterIn, High Seas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryViewpointCharacterIn Context triple: [Victor, primaryViewpointCharacterIn, High Seas]
-
A.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
B.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
C.
primaryPerspective
Indicates that one entity serves as the main or dominant viewpoint, angle, or interpretive frame through which another entity is understood, presented, or analyzed.
-
D.
primaryPersona
Indicates that one entity is the main or most representative persona associated with another entity, distinguishing it from any secondary or supporting personas.
-
E.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3933e71ad48190a31c8a6ada1c5c71 |
completed | June 22, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.