Triple
T24313740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gale’s top trading cycles algorithm |
E612746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | allocation mechanism |
C9004
|
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: allocation mechanism Context triple: [Gale’s top trading cycles algorithm, instanceOf, allocation mechanism]
-
A.
seat allocation method
chosen
A seat allocation method is a systematic procedure or algorithm used to assign available seats (such as in a legislature, classroom, or venue) to eligible entities based on predefined rules or criteria.
-
B.
allocation table
An allocation table is a structured record that maps and tracks how resources, such as memory, funds, or tasks, are distributed among various entities or categories.
-
C.
DDR coordination mechanism
A DDR coordination mechanism is a structured framework of processes, roles, and tools that align and synchronize disarmament, demobilization, and reintegration activities among stakeholders to ensure coherent, efficient, and conflict-sensitive implementation.
-
D.
quota system
A quota system is a structured mechanism that sets fixed numerical or proportional limits or targets—such as for production, imports, or representation—to regulate distribution, access, or participation within a defined context.
-
E.
arms transfer mechanism
An arms transfer mechanism is a system or process that facilitates the legal or illegal movement, sale, or provision of weapons and related military equipment between parties, such as states, organizations, or individuals.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:45 a.m.