Triple
T27705168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unified Socialist Party (France) |
E698533
|
entity |
| Predicate | hadElectoralStrength |
P162966
|
FINISHED |
| Object | small |
—
|
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: small | Statement: [Unified Socialist Party (France), hadElectoralStrength, small]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadElectoralStrength Context triple: [Unified Socialist Party (France), hadElectoralStrength, small]
-
A.
hasElectoralStronghold
Indicates that a political entity consistently receives dominant or reliable electoral support in a particular area or constituency.
-
B.
electoralSuccess
Indicates that an entity has achieved a favorable or winning outcome in an election or electoral process.
-
C.
hasElectoralVoteIn
Indicates that an entity possesses or receives electoral votes within a specified election or jurisdiction.
-
D.
hasElectoralStrategy
Indicates that an entity employs or is associated with a specific plan or approach for winning or influencing an election.
-
E.
hasElectoralAuthority
Indicates that an entity possesses the official power or legal right to oversee, manage, or make binding decisions about electoral processes or outcomes.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f635a632788190b483e2baff237255 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f62c1a92648190835a2c5250d8c758 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f6305219f08190b55f6193a4a49984 |
completed | May 2, 2026, 5:11 p.m. |
Created at: April 27, 2026, 2:59 p.m.