Triple
T35171242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangalle Beach |
E1015549
|
entity |
| Predicate | hasNearbyWildlifeInterest |
P34896
|
FINISHED |
| Object | sea turtle nesting sites at Rekawa |
—
|
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: sea turtle nesting sites at Rekawa | Statement: [Tangalle Beach, hasNearbyWildlifeInterest, sea turtle nesting sites at Rekawa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWildlifeInterest Context triple: [Tangalle Beach, hasNearbyWildlifeInterest, sea turtle nesting sites at Rekawa]
-
A.
hasNearbyWildlife
chosen
Indicates that there is wildlife located close to or in the immediate vicinity of the referenced entity.
-
B.
hasWildlifeActivity
Indicates that wildlife is present in the area and engaging in observable behaviors or movements.
-
C.
hasWildlifeObservation
Indicates that a wildlife observation event or record is associated with a particular entity (such as a location, time, or observer).
-
D.
hasWildlifeFocus
Indicates that something is primarily concerned with, dedicated to, or centered around wildlife.
-
E.
hasNearbyWildlifeRefuge
Indicates that something is located close to or in the vicinity of a designated wildlife refuge.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: May 3, 2026, 4:02 p.m.