Triple
T29709930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagapattinam district |
E751749
|
entity |
| Predicate | hasCoastalVillages |
P100515
|
FINISHED |
| Object | fishing hamlets |
—
|
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 hamlets | Statement: [Nagapattinam district, hasCoastalVillages, fishing hamlets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoastalVillages Context triple: [Nagapattinam district, hasCoastalVillages, fishing hamlets]
-
A.
hasTraditionalVillagesAlongCoast
chosen
Indicates that there are traditional villages located along the coastline of a specified geographic area.
-
B.
hasCoastalMunicipalities
Indicates that a region or higher-level area includes one or more municipalities that are located along a sea or ocean coastline.
-
C.
hasCoastalDistrict
Indicates that an administrative region or area includes at least one district that borders a sea or ocean.
-
D.
hasNearbyCoastalSettlement
Indicates that one entity has a coastal settlement located in close geographic proximity to it.
-
E.
hasCoastalSection
Indicates that a geographic entity includes at least one section of land that directly borders a sea 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_69f0d62748848190b030d0a703629a7d |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a009a0e1fa481909ed881012009b268 |
completed | May 10, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_6a0092e9fcb08190a966d720684f25ec |
completed | May 10, 2026, 2:15 p.m. |
Created at: April 28, 2026, 7:30 p.m.