Triple
T28971050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Demons |
E734272
|
entity |
| Predicate | nearbyHumanActivity |
P71206
|
FINISHED |
| Object | local fishing in surrounding coastal areas |
—
|
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: local fishing in surrounding coastal areas | Statement: [Bay of Demons, nearbyHumanActivity, local fishing in surrounding coastal areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyHumanActivity Context triple: [Bay of Demons, nearbyHumanActivity, local fishing in surrounding coastal areas]
-
A.
nearbyActivity
Indicates that an activity occurs close in space or proximity to a specified entity or location.
-
B.
nearbyActivityHub
Indicates that one entity is located close enough to another entity that serves as a central hub or focal point for activities or events.
-
C.
nearbyEvent
Indicates that one event occurs close in space or time to another event.
-
D.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
E.
nearbyEconomicActivity
chosen
Indicates that there is economic activity occurring in close physical proximity to the referenced entity.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 28, 2026, 9:05 a.m.