Triple
T29944908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherai Beach |
E760603
|
entity |
| Predicate | hasBackwaters |
P64067
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cherai Beach, hasBackwaters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackwaters Context triple: [Cherai Beach, hasBackwaters, yes]
-
A.
usesWaterwaysFor
Indicates that one entity relies on or employs waterways as a means or route to perform an activity or function in relation to another entity.
-
B.
associatedWithWaterways
Indicates a relationship in which something is connected, linked, or relevant to waterways such as rivers, canals, or streams.
-
C.
hasWaterFeatures
chosen
Indicates that an entity includes or is associated with water-related elements such as fountains, ponds, streams, or similar features.
-
D.
hasFreshwaterSection
Indicates that an entity includes or contains a distinct section or area composed of freshwater.
-
E.
hasWaterfrontAccessTo
Indicates that one entity is directly adjacent to and can physically access a particular body of water, such as a lake, river, or ocean.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 29, 2026, 6:23 p.m.