Triple
T323344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of Moscow |
E6461
|
entity |
| Predicate | hasAuthorityTo |
P2231
|
FINISHED |
| Object | issue mayoral decrees in Moscow |
—
|
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: issue mayoral decrees in Moscow | Statement: [Mayor of Moscow, hasAuthorityTo, issue mayoral decrees in Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorityTo Context triple: [Mayor of Moscow, hasAuthorityTo, issue mayoral decrees in Moscow]
-
A.
hasAuthorityStatus
chosen
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
-
B.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
C.
hasRole
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
D.
isGrantedFor
Indicates that a permission, right, or benefit has been formally given to a specific entity for a particular purpose or use.
-
E.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.