Triple
T25197156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nancy Downs |
E631030
|
entity |
| Predicate | laterBecomesEnemyOf |
P89510
|
FINISHED |
| Object | Sarah Bailey |
—
|
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: Sarah Bailey | Statement: [Nancy Downs, laterBecomesEnemyOf, Sarah Bailey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterBecomesEnemyOf Context triple: [Nancy Downs, laterBecomesEnemyOf, Sarah Bailey]
-
A.
laterEnemyOf
chosen
Indicates that one entity becomes an enemy of another at a later time, after not initially being in an antagonistic relationship.
-
B.
formerEnemyOf
Indicates that one entity was previously an enemy of another entity, but that adversarial relationship no longer holds.
-
C.
initiallyEnemyOf
Indicates that one entity starts out in a state of enmity or opposition toward another at the beginning of a specified time or situation.
-
D.
temporarilyEnemyOf
Indicates a relationship where two entities are in a state of enmity or opposition for a limited, non-permanent period of time.
-
E.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 21, 2026, 12:50 p.m.