Triple
T19158821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ħamrun |
E468996
|
entity |
| Predicate | hasBusRouteHub |
P5891
|
FINISHED |
| Object | Ħamrun bus stops on main arterial road |
—
|
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: Ħamrun bus stops on main arterial road | Statement: [Ħamrun, hasBusRouteHub, Ħamrun bus stops on main arterial road]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusRouteHub Context triple: [Ħamrun, hasBusRouteHub, Ħamrun bus stops on main arterial road]
-
A.
hasTransportHub
Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
-
B.
hasBusStation
chosen
Indicates that a place or area contains or is served by a bus station.
-
C.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
-
D.
isTransportHubType
Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
-
E.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eebb573081909fcd6af8aff8692b |
completed | April 20, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.