Triple
T33917657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carmen |
E869507
|
entity |
| Predicate | mainConflictWith |
P5022
|
FINISHED |
| Object | Ana García |
—
|
NE NERFINISHED |
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: Ana García | Statement: [Carmen, mainConflictWith, Ana García]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainConflictWith Context triple: [Carmen, mainConflictWith, Ana García]
-
A.
conflictWith
Indicates that two entities are in opposition or disagreement, such that their goals, actions, or states are incompatible or interfere with each other.
-
B.
mainConflict
chosen
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
C.
mentionsConflict
Indicates that one entity refers to or discusses a dispute, disagreement, or conflict involving another entity.
-
D.
subConflict
Indicates that one conflict is a component, phase, or subordinate part of a larger overarching conflict.
-
E.
reportedConflict
Indicates that one party has formally reported the existence of a conflict involving another party or situation.
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcef654d588190b29ecc76678d1aa0 |
completed | May 7, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69fcecdb97f48190b382b7d13be92dc0 |
completed | May 7, 2026, 7:49 p.m. |
Created at: May 1, 2026, 1:48 a.m.