Triple
T14705266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Désirée |
E345412
|
entity |
| Predicate | storyConflictSource |
P115433
|
FINISHED |
| Object | uncertain ancestry |
—
|
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: uncertain ancestry | Statement: [Désirée, storyConflictSource, uncertain ancestry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyConflictSource Context triple: [Désirée, storyConflictSource, uncertain ancestry]
-
A.
storyConflict
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
-
B.
conflictSource
Indicates that one entity is the origin, cause, or initiating side of a conflict involving another entity.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
originatingConflict
Indicates the conflict or dispute from which another event, situation, or relationship initially arises or is caused.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- F. None of above. chosen
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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb6086c608190a66c64e23a3e002f |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716d3aac8190aaa6dc1f099b86e8 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:28 a.m.