Triple
T34982309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation–Cardassian border realignment |
E1008847
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political settlement |
C964
|
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: political settlement Context triple: [Federation–Cardassian border realignment, instanceOf, political settlement]
-
A.
political situation
A political situation is the current state of affairs shaped by the interactions, power dynamics, and decisions of governments, political actors, and institutions within a specific context.
-
B.
political agreement
chosen
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
C.
political partition
A political partition is the formal division of a territory or state into separate political entities, typically through legal or diplomatic processes, often reshaping borders, governance, and national identities.
-
D.
political transition
A political transition is the process by which a political system, regime, or leadership changes from one form or ruling group to another, often involving shifts in institutions, power structures, and governance practices.
-
E.
regional settlement system
A regional settlement system is the interconnected network of cities, towns, and rural areas within a region, shaped by flows of people, goods, services, and information and structured by economic, social, and environmental relationships.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.