Triple
T8229114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Party (Greece) |
E192244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical political faction |
C1884
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical political faction Context triple: [French Party (Greece), instanceOf, historical political faction]
-
A.
medieval political faction
A medieval political faction is an organized group of nobles, clergy, or urban elites who align around shared interests, loyalties, or claims to power, competing and negotiating within the feudal and dynastic structures of the Middle Ages.
-
B.
historical political system
A historical political system is an organized structure of governance, power relations, and institutions that operated within a specific society and time period, shaping how authority was distributed, exercised, and justified.
-
C.
historical group
chosen
A historical group is a collection of people connected by a shared identity, purpose, or activity that existed and acted within a specific past time period.
-
D.
judicial faction
A judicial faction is a group of judges or legal decision-makers within a court system who share similar interpretive philosophies, policy preferences, or ideological leanings that influence their collective rulings and legal strategies.
-
E.
Florentine political faction
A Florentine political faction is a historically rooted group within Florence’s civic life that organized around shared social, economic, or ideological interests to compete for power and influence in the city’s government and public affairs.
- F. None of above.
Provenance (1 batch)
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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:46 p.m.