Triple
T2974253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Vicomte of Bragelonne |
E80354
|
entity |
| Predicate | notableCharacterArc |
P36856
|
FINISHED |
| Object | aging of the original Musketeers |
—
|
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: aging of the original Musketeers | Statement: [The Vicomte of Bragelonne, notableCharacterArc, aging of the original Musketeers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCharacterArc Context triple: [The Vicomte of Bragelonne, notableCharacterArc, aging of the original Musketeers]
-
A.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
B.
characterArcElement
chosen
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
C.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
D.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
-
E.
notableCharacterCreated
Indicates that one entity is a notable or significant character that was created by 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_69ad8b14ffe881908ffed62f9595c867 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99894bb0819099fa5cc5166c0eeb |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad96105a708190a9ec4838cbcb1207 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.