Triple
T27722577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nellore district |
E698999
|
entity |
| Predicate | hasCoastalEconomyActivity |
P199367
|
FINISHED |
| Object | fishing |
—
|
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: fishing | Statement: [Nellore district, hasCoastalEconomyActivity, fishing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalEconomyActivity Context triple: [Nellore district, hasCoastalEconomyActivity, fishing]
-
A.
hasCoastalFunction
Indicates that something serves a role, purpose, or activity specifically related to the coast or coastal areas.
-
B.
hasCoastalRegion
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
C.
hasCoastalEnvironment
Indicates that an entity is located in, adjacent to, or characterized by a coastal environment or shoreline setting.
-
D.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
E.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
- F. None of above. chosen
Provenance (4 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_69ef591012dc8190a6f1ec994f9f7ff7 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: April 27, 2026, 3:07 p.m.