Triple
T13194660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rose Chapotel |
E314079
|
entity |
| Predicate | centralConflictInvolves |
P96925
|
FINISHED |
| Object | marital status |
—
|
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: marital status | Statement: [Rose Chapotel, centralConflictInvolves, marital status]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralConflictInvolves Context triple: [Rose Chapotel, centralConflictInvolves, marital status]
-
A.
centralConflictIn
chosen
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
B.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
internalConflict
Indicates a relationship where an entity experiences opposing desires, beliefs, or motives within itself, leading to psychological or emotional tension.
-
E.
addressesConflictWithin
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.