Triple
T28669227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Man Warner |
E725663
|
entity |
| Predicate | opposesChangeTo |
P39123
|
FINISHED |
| Object | the lottery |
—
|
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: the lottery | Statement: [Old Man Warner, opposesChangeTo, the lottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesChangeTo Context triple: [Old Man Warner, opposesChangeTo, the lottery]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
-
C.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
D.
opposedConversionOf
chosen
Indicates that one entity actively resisted, objected to, or worked against the process of converting or changing another entity.
-
E.
opposesDivision
Indicates a relationship where one entity actively resists, rejects, or works against the separation or splitting of another entity into parts or groups.
- 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_69f01d85be388190b669a0e401e2f2c4 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 5:02 a.m.