Triple
T31598038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perry Wright |
E806271
|
entity |
| Predicate | causeOfConflictWith |
P61068
|
FINISHED |
| Object | Celeste Wright |
—
|
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: Celeste Wright | Statement: [Perry Wright, causeOfConflictWith, Celeste Wright]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfConflictWith Context triple: [Perry Wright, causeOfConflictWith, Celeste Wright]
-
A.
hasCauseOfConflict
chosen
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
-
B.
causeOfPoliticalConflict
Indicates that one entity is the source or reason for a political conflict involving another entity.
-
C.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
D.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
E.
reasonForConflict
Indicates that one entity is the cause, motive, or underlying issue leading to a conflict involving another entity.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 30, 2026, 10:31 p.m.