Triple
T32552683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Machines |
E832014
|
entity |
| Predicate | turnAgainst |
P174588
|
FINISHED |
| Object | their human creators |
—
|
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: their human creators | Statement: [the Machines, turnAgainst, their human creators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: turnAgainst Context triple: [the Machines, turnAgainst, their human creators]
-
A.
turningPointAgainst
Indicates a pivotal moment or event that shifts momentum or advantage against a particular entity or side.
-
B.
turnedHeel
Indicates that an entity abruptly reversed direction or changed course, often implying a sudden shift in stance or behavior.
-
C.
turns
Indicates a change in orientation, direction, or state initiated by one entity affecting itself or another entity.
-
D.
ledAgainst
Indicates that one entity directed or commanded an opposing effort, campaign, or force against another entity.
-
E.
antagonisticArc
Indicates a relationship in which one entity consistently opposes, harms, or works against another over the course of a conflict or storyline.
- F. None of above. chosen
Provenance (4 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_69f34926b9848190ace47d2dd0a0de7c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c7c66c8190a6895a998729fe69 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.