Triple
T860148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian National Congress |
E18580
|
entity |
| Predicate | dominantPartySystemPeriod |
P8471
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [Indian National Congress, dominantPartySystemPeriod, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPartySystemPeriod Context triple: [Indian National Congress, dominantPartySystemPeriod, 1950s]
-
A.
dominantPartySystem
Indicates a political system in which one party consistently dominates governance over time, despite the presence of other legally allowed parties.
-
B.
historicalDominantParties
chosen
Indicates that certain political parties have historically held dominant or ruling positions within a given political system or jurisdiction.
-
C.
dominantParty
Indicates that one party in a relationship holds primary control, authority, or influence over the other.
-
D.
democraticPeriod
Indicates a time span during which a political system or government operates under democratic principles and institutions.
-
E.
electoralAlliancePeriod
Indicates the time span during which two or more political entities are formally joined in an electoral alliance.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.