Triple
T3030320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comte de la Fère |
E82877
|
entity |
| Predicate | literaryArchetype |
P15535
|
FINISHED |
| Object | tragic nobleman |
—
|
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: tragic nobleman | Statement: [Comte de la Fère, literaryArchetype, tragic nobleman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: literaryArchetype Context triple: [Comte de la Fère, literaryArchetype, tragic nobleman]
-
A.
literaryRole
chosen
Indicates the specific narrative or functional role an entity holds within a literary work or text.
-
B.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
D.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9aecd384819085d15f701add7c44 |
completed | March 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.