Triple
T27739594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eva Dandridge |
E701814
|
entity |
| Predicate | conflictSourceFor |
P48690
|
FINISHED |
| Object | her sisters’ romantic relationships |
—
|
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: her sisters’ romantic relationships | Statement: [Eva Dandridge, conflictSourceFor, her sisters’ romantic relationships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictSourceFor Context triple: [Eva Dandridge, conflictSourceFor, her sisters’ romantic relationships]
-
A.
conflictSource
chosen
Indicates that one entity is the origin, cause, or initiating side of a conflict involving another entity.
-
B.
conflictLocation
Indicates the place or geographic area where a conflict, dispute, or confrontation occurs or is centered.
-
C.
storyConflictSource
Indicates the source or cause from which a story’s central conflict arises.
-
D.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified entity or process.
-
E.
conflictContext
Indicates the situational background or circumstances within which a conflict between entities occurs or is interpreted.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 4:09 p.m.