Triple
T8416227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Party |
E198735
|
entity |
| Predicate | claimsStateForm |
P35007
|
FINISHED |
| Object | oligarchical collectivism |
—
|
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: oligarchical collectivism | Statement: [The Party, claimsStateForm, oligarchical collectivism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimsStateForm Context triple: [The Party, claimsStateForm, oligarchical collectivism]
-
A.
claimProcess
Indicates the process by which a claim (such as an insurance or service claim) is received, evaluated, and resolved between involved parties.
-
B.
counterClaimantState
Indicates a relationship where a state formally presents a counter-claim in response to an existing claim, typically in a legal or dispute-resolution context.
-
C.
originalClaimedForm
Indicates that one entity is asserted to be the initial or first version/form in which another entity was claimed or presented.
-
D.
stateForm
chosen
Indicates that an entity has the political or constitutional form of a particular state or system of government.
-
E.
claimMethod
Indicates the method or procedure by which a claim is made, submitted, or executed.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c5121081908efa3eca25406d3a |
completed | March 31, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.