Triple
T12590109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan District of Caracas |
E300579
|
entity |
| Predicate | hasPolicyScope |
P397
|
FINISHED |
| Object | inter-municipal coordination |
—
|
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: inter-municipal coordination | Statement: [Metropolitan District of Caracas, hasPolicyScope, inter-municipal coordination]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicyScope Context triple: [Metropolitan District of Caracas, hasPolicyScope, inter-municipal coordination]
-
A.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
-
C.
hasPolicySupport
Indicates that one entity provides endorsement, backing, or approval for a specific policy associated with another entity.
-
D.
hasPolicyFunction
Indicates that an entity is associated with, governed by, or characterized through a particular policy function or set of policy rules.
-
E.
containsPolicyOn
Indicates that one entity includes, references, or incorporates a specific policy within 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:07 p.m.