Triple
T34333927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Region of Malta |
E881093
|
entity |
| Predicate | containsLocalCouncil |
P200075
|
FINISHED |
| Object | Mellieħa |
—
|
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: Mellieħa | Statement: [Northern Region of Malta, containsLocalCouncil, Mellieħa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLocalCouncil Context triple: [Northern Region of Malta, containsLocalCouncil, Mellieħa]
-
A.
hasLocalCouncilArea
chosen
Indicates that an entity is located within, or is administratively governed by, a specific local council area.
-
B.
containsRegionalCouncil
Indicates that one administrative or geographic entity includes a regional council within its jurisdiction or boundaries.
-
C.
locatedInRegionalCouncil
Indicates that one entity is geographically situated within the jurisdictional area governed by a specific regional council.
-
D.
districtCouncil
Indicates that an entity serves as, or is governed by, a district-level council within a larger administrative or political structure.
-
E.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
Created at: May 1, 2026, 1:58 a.m.