Triple
T3583632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CO |
E75857
|
entity |
| Predicate | governsCodeElementsFor |
P760
|
FINISHED |
| Object | sovereign state |
—
|
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: sovereign state | Statement: [CO, governsCodeElementsFor, sovereign state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsCodeElementsFor Context triple: [CO, governsCodeElementsFor, sovereign state]
-
A.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
B.
governedInPartBy
Indicates that something is subject to the authority, control, or influence of a governing entity, but only to a limited or partial extent rather than fully.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
governingBodyForRules
Indicates that an entity serves as the official authority responsible for creating, maintaining, or enforcing a specified set of rules.
-
E.
governedWith
Indicates that two or more entities share or participate together in the act or process of governing.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc104846c81908b6fbde7061464b4 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.