Triple
T30868034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jiusan Society |
E786256
|
entity |
| Predicate | numberOfMajorMinorPartiesInSystem |
P34865
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [Jiusan Society, numberOfMajorMinorPartiesInSystem, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMajorMinorPartiesInSystem Context triple: [Jiusan Society, numberOfMajorMinorPartiesInSystem, 8]
-
A.
hasNumberOfParties
chosen
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
B.
hasMajorParties
Indicates that an entity is associated with its primary participating parties or main involved groups.
-
C.
numberOfPartiesWinningSeats
Indicates the total count of distinct parties that have secured at least one seat in an election or representative body.
-
D.
numberOfPartiesInChamber
Indicates the total count of distinct parties represented within a specific legislative chamber.
-
E.
multiPartySystem
Indicates a relationship in which more than two distinct parties or entities are jointly involved in a shared process, interaction, or system.
- 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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: April 29, 2026, 8:47 p.m.