Triple
T14067308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turks Islands |
E338507
|
entity |
| Predicate | hasMarineAttraction |
P42408
|
FINISHED |
| Object | whale watching |
—
|
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: whale watching | Statement: [Turks Islands, hasMarineAttraction, whale watching]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarineAttraction Context triple: [Turks Islands, hasMarineAttraction, whale watching]
-
A.
hasMarinePark
Indicates that an entity possesses, contains, or is associated with a designated marine park area.
-
B.
marineAttraction
chosen
Indicates a relationship where one entity serves as a point of interest or entertainment specifically related to marine life or the marine environment for another entity.
-
C.
hasMarineHabitatType
Indicates that an entity is associated with or occurs in a specific type of marine habitat.
-
D.
hasMaritimeMuseum
Indicates that one entity possesses, hosts, or includes a maritime museum as part of its features or facilities.
-
E.
hasBeach
Indicates that one entity possesses, includes, or is characterized by a beach as part of its features or environment.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568b81f08190a571004261c0e8e4 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.