Triple
T2569783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Committee |
E57635
|
entity |
| Predicate | typicalSelectionMethod |
P11413
|
FINISHED |
| Object | elected by Party Congress delegates |
—
|
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: elected by Party Congress delegates | Statement: [Central Committee, typicalSelectionMethod, elected by Party Congress delegates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSelectionMethod Context triple: [Central Committee, typicalSelectionMethod, elected by Party Congress delegates]
-
A.
typicalNumberOfSelections
Indicates the usual or expected count of selections made in a given choice or selection process.
-
B.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
C.
grantSelectionMethod
Indicates the method or criteria by which a grant is chosen or awarded among potential candidates.
-
D.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
E.
hasMemberSelectionMethod
chosen
Indicates the method or criteria by which members of a group, organization, or body are chosen or selected.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd380d6e081909c124e8a0b7feef3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cc8d308190ae7aa32b8f5ae2e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.