Triple
T14275982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Council of the Time Lords |
E353916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supreme council |
C308
|
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: supreme council Context triple: [High Council of the Time Lords, instanceOf, supreme council]
-
A.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
B.
council of magistrates
A council of magistrates is a governing body composed of appointed or elected judicial and administrative officials responsible for overseeing the application of laws, adjudicating disputes, and managing public affairs within a jurisdiction.
-
C.
Dewan
Dewan is a conceptual class representing a formal council or advisory body that provides guidance, deliberation, and decision-making support within a governance or organizational structure.
-
D.
supreme soviet
The Supreme Soviet was the highest legislative body in the Soviet Union (and in its constituent republics), formally empowered to enact laws, approve plans and budgets, and elect key state officials, though in practice it largely ratified decisions made by the Communist Party leadership.
-
E.
Verteidigungsausschuss
Der Verteidigungsausschuss ist ein parlamentarisches Gremium, das die Verteidigungs- und Sicherheitspolitik eines Staates überwacht, Gesetzentwürfe im Verteidigungsbereich berät und die Arbeit des Verteidigungsministeriums kontrolliert.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:10 a.m.