Triple
T28218971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runaway Horses |
E711396
|
entity |
| Predicate | containsPoliticalConspiracy |
P97194
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Runaway Horses, containsPoliticalConspiracy, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPoliticalConspiracy Context triple: [Runaway Horses, containsPoliticalConspiracy, yes]
-
A.
conspiracy
Indicates a secret agreement or collaboration between multiple entities to plan or carry out an unlawful, deceptive, or harmful act.
-
B.
conspiracyType
Indicates the specific category or nature of a conspiracy associated with an entity or event.
-
C.
conspirator
Indicates that an entity participates with others in planning or carrying out a secret or illicit scheme or action.
-
D.
positionOnConspiracy
Indicates the stance or viewpoint an entity holds regarding a particular conspiracy or conspiracy theory.
-
E.
hasPoliticalPlot
chosen
Indicates that the subject work contains a storyline or narrative element centered on politics, political events, or political power struggles.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: April 27, 2026, 10:45 p.m.