Triple
T34333911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comino coastline |
E881092
|
entity |
| Predicate | boatTraffic |
P118148
|
FINISHED |
| Object | heavy in peak season |
—
|
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: heavy in peak season | Statement: [Comino coastline, boatTraffic, heavy in peak season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boatTraffic Context triple: [Comino coastline, boatTraffic, heavy in peak season]
-
A.
shipTraffic
chosen
Indicates the presence, movement, or volume of ships traveling through a particular waterway or maritime area.
-
B.
managesWaterwayTraffic
Indicates that an entity is responsible for directing, regulating, or overseeing the movement of vessels and other traffic along a waterway.
-
C.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
D.
supportsBargeTrafficTo
Indicates that one entity enables or facilitates barge traffic or navigation to another entity.
-
E.
travelTimeByBoat
Indicates the amount of time it takes to travel between two locations specifically when using a boat as the mode of transportation.
- 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_69f71c35327c8190884f1bfe12bd2cd7 |
completed | May 3, 2026, 9:58 a.m. |
| PD | Predicate disambiguation | batch_69f71822d0e88190ac9731c7ae5a4def |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 1:58 a.m.