Triple
T28904374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emmanuel Goldstein |
E733033
|
entity |
| Predicate | allegedLeaderOf |
P176728
|
FINISHED |
| Object | The Brotherhood |
—
|
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 Brotherhood | Statement: [Emmanuel Goldstein, allegedLeaderOf, The Brotherhood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedLeaderOf Context triple: [Emmanuel Goldstein, allegedLeaderOf, The Brotherhood]
-
A.
coupLeader
Indicates that the subject is the primary organizer or head figure responsible for leading a coup against an existing authority.
-
B.
belligerentLeader
Indicates that an entity serves as a leader or authority figure of a party engaged in a conflict, war, or hostile confrontation.
-
C.
hadPrincipalLeader
Indicates that an entity was led or headed by a primary or chief leader.
-
D.
coupLeaderOpposedBy
Indicates that the identified coup leader is actively resisted, challenged, or opposed by another specified party.
-
E.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 28, 2026, 8:05 a.m.