Triple
T29794937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boulder Free Zone |
E756518
|
entity |
| Predicate | opposedToLeader |
P19546
|
FINISHED |
| Object | Randall Flagg |
—
|
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: Randall Flagg | Statement: [Boulder Free Zone, opposedToLeader, Randall Flagg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedToLeader Context triple: [Boulder Free Zone, opposedToLeader, Randall Flagg]
-
A.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
B.
opposedLeader
chosen
Indicates that one entity actively resisted, challenged, or worked against the leadership or authority of another entity.
-
C.
coupLeaderOpposedBy
Indicates that the identified coup leader is actively resisted, challenged, or opposed by another specified party.
-
D.
opposedLeaderSide2
Indicates that the second leader or side is in opposition to another leader or side in a conflict or contest.
-
E.
primaryOpposingLeader
Indicates that one entity serves as the main or chief leader directly opposing another entity in a conflict, competition, or political context.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 29, 2026, 5:14 p.m.