Triple
T4029194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Citadel |
E83664
|
entity |
| Predicate | governedSystem |
P28368
|
FINISHED |
| Object | Time Lord legal system |
—
|
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: Time Lord legal system | Statement: [The Citadel, governedSystem, Time Lord legal system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedSystem Context triple: [The Citadel, governedSystem, Time Lord legal system]
-
A.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
-
B.
governedThrough
Indicates that one entity exercises control, authority, or administration over another entity by means of a specified intermediary mechanism, structure, or process.
-
C.
governedAs
Indicates that one entity exercises authoritative control, direction, or rule over another according to some system of governance or leadership.
-
D.
governingSystemContext
chosen
Indicates the broader political, legal, or organizational system within which an action, decision, or relationship is defined and regulated.
-
E.
governed by
Indicates that an entity is under the authority, control, or administration of another entity that makes and enforces rules or decisions for it.
- 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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaf066b08190afbb4a18ddc8d67e |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fe440c819093a7fa22c4ff3f1a |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:36 p.m.