Triple
T3765066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Swede |
E82651
|
entity |
| Predicate | hasBackstoryElement |
P38047
|
FINISHED |
| Object | former Union soldier |
—
|
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: former Union soldier | Statement: [The Swede, hasBackstoryElement, former Union soldier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackstoryElement Context triple: [The Swede, hasBackstoryElement, former Union soldier]
-
A.
hasProtagonistBackground
Indicates that a work or narrative features a specified background or origin story for its main protagonist.
-
B.
protagonistBackground
chosen
Indicates that one entity serves as the background, history, or prior circumstances of the protagonist entity in a narrative or story.
-
C.
hasOriginStoryLocation
Indicates that an entity’s origin story takes place at or is associated with a specific location.
-
D.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
E.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfeb52081909c38103beb5dbdcd |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.