Triple
T34333959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Region of Malta |
E881093
|
entity |
| Predicate | containsRuralVillage |
P54976
|
FINISHED |
| Object | Mġarr |
—
|
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: Mġarr | Statement: [Northern Region of Malta, containsRuralVillage, Mġarr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRuralVillage Context triple: [Northern Region of Malta, containsRuralVillage, Mġarr]
-
A.
hasVillage
Indicates that an entity possesses, contains, or is associated with a village.
-
B.
hasRuralLocality
chosen
Indicates that an entity possesses, includes, or is associated with a rural locality (such as a village, hamlet, or countryside settlement) within its scope or jurisdiction.
-
C.
hasRuralArea
Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
-
D.
hasVillageCommunity
Indicates that an entity possesses, is associated with, or includes a village-level community as part of its structure or domain.
-
E.
hasRuralSection
Indicates that an entity includes, contains, or is associated with a portion or segment located in a rural area.
- 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_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 1, 2026, 1:58 a.m.