Triple
T25163574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | municipality of Belgrade |
E626507
|
entity |
| Predicate | hasStatutoryDocument |
P9087
|
FINISHED |
| Object | municipal statute |
—
|
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: municipal statute | Statement: [municipality of Belgrade, hasStatutoryDocument, municipal statute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatutoryDocument Context triple: [municipality of Belgrade, hasStatutoryDocument, municipal statute]
-
A.
hasOfficialDocument
Indicates that an entity possesses or is associated with a formal, authorized document issued by a recognized authority.
-
B.
hasNotableDocument
Indicates that an entity is associated with a document that is considered significant, noteworthy, or of particular importance.
-
C.
hasDOC
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
D.
hasStatutes
Indicates that one entity possesses, is governed by, or is associated with a set of formal laws or statutes defined by another entity.
-
E.
hasLegalInstrument
chosen
Indicates that there exists a formal legal document or instrument that establishes, governs, or records the relationship between the related entities.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 18, 2026, 6:31 a.m.