Triple
T323236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of Moscow |
E6459
|
entity |
| Predicate | appliesPolicy |
P1051
|
FINISHED |
| Object | urban development policy of 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: urban development policy of Moscow | Statement: [Government of Moscow, appliesPolicy, urban development policy of Moscow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesPolicy Context triple: [Government of Moscow, appliesPolicy, urban development policy of Moscow]
-
A.
implementedPolicy
Indicates that a particular policy has been put into effect or carried out by an entity.
-
B.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
C.
admissionPolicy
Indicates the rules or criteria governing whether and how entities are allowed to be admitted or granted access.
-
D.
policyTool
Indicates that an entity is a tool, mechanism, or instrument used to design, implement, or enforce a policy.
-
E.
governingPolicy
chosen
Indicates that one entity serves as the authoritative policy or set of rules that directs, constrains, or regulates the behavior, operation, or decisions of another entity.
- 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.