Triple
T36143072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipality of Deçan |
E1045366
|
entity |
| Predicate | hasLocalAssembly |
P38394
|
FINISHED |
| Object | Assembly of the Municipality of Deçan |
—
|
NE NERFINISHED |
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: Assembly of the Municipality of Deçan | Statement: [Municipality of Deçan, hasLocalAssembly, Assembly of the Municipality of Deçan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocalAssembly Context triple: [Municipality of Deçan, hasLocalAssembly, Assembly of the Municipality of Deçan]
-
A.
hadLocalAssembly
chosen
Indicates that an entity hosted or possessed a local-level governing or decision-making assembly within its jurisdiction or area.
-
B.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
C.
hasAssemblyType
Indicates that an entity is associated with or classified by a specific type or method of assembly.
-
D.
hasAssemblySegment
Indicates that an object or system includes a specific segment as part of its overall assembly structure.
-
E.
hasCheckOnAssembly
Indicates that an assembly is subject to a specific inspection, verification, or quality check.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff46afe7e481908f2862ed11c88db2 |
completed | May 9, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69ff45e9151881909c444a655e852165 |
completed | May 9, 2026, 2:34 p.m. |
Created at: May 3, 2026, 4:08 p.m.