Triple
T12624964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Għasri |
E301486
|
entity |
| Predicate | hasCoastalActivity |
P103251
|
FINISHED |
| Object | swimming at Wied il-Għasri |
—
|
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: swimming at Wied il-Għasri | Statement: [Għasri, hasCoastalActivity, swimming at Wied il-Għasri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalActivity Context triple: [Għasri, hasCoastalActivity, swimming at Wied il-Għasri]
-
A.
hasCoastalRecreation
chosen
Indicates that an entity provides, supports, or is associated with recreational activities occurring along a coast or shoreline.
-
B.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
C.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea or ocean.
-
D.
hasCoastalCharacteristic
Indicates that an entity possesses a feature, quality, or condition specifically related to coastal or shoreline environments.
-
E.
isCoastalOn
Indicates that one entity is located along or directly borders the coastline of another entity (such as a body of water or sea).
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:14 p.m.