Triple
T34383524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Il-Port il-Kbir |
E882499
|
entity |
| Predicate | adjacentLocality |
P5707
|
FINISHED |
| Object | Floriana |
—
|
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: Floriana | Statement: [Il-Port il-Kbir, adjacentLocality, Floriana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentLocality Context triple: [Il-Port il-Kbir, adjacentLocality, Floriana]
-
A.
hasNeighbouringLocality
Indicates that one locality is geographically adjacent to or directly borders another locality.
-
B.
locatedInOrAdjacentTo
Indicates that one entity is either situated within the boundaries of another entity or directly next to it, sharing a common border or edge.
-
C.
localityOf
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
D.
isAdjacentTo
chosen
Indicates that one entity is directly next to or bordering another without anything of the same type in between.
-
E.
associatedWithLocality
Indicates a relationship where something has a connection or relevance to a specific geographic place or locality.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 1, 2026, 1:59 a.m.