Triple
T33019037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiruvarur district |
E844852
|
entity |
| Predicate | agroClimateZone |
P175922
|
FINISHED |
| Object | Cauvery delta zone |
—
|
NE NERFINISHED |
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: Cauvery delta zone | Statement: [Tiruvarur district, agroClimateZone, Cauvery delta zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agroClimateZone Context triple: [Tiruvarur district, agroClimateZone, Cauvery delta zone]
-
A.
shareClimateZones
Indicates that two entities are located in regions classified under the same climate zone or zones.
-
B.
climatologicalRegion
Indicates that one entity is a climatological region associated with, or characterizing the climate of, another entity.
-
C.
climateZonesShowcased
Indicates that certain climate zones are being presented or highlighted, typically for display, comparison, or informational purposes.
-
D.
shareAgriculturalZone
Indicates that two or more entities are located within or assigned to the same agricultural zone or region for cultivation or land-use purposes.
-
E.
FAOArea
Indicates that an entity is associated with a specific geographic area as defined by the Food and Agriculture Organization (FAO) classification system.
- 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_69f3494f3b4081909dccf2af34372a26 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d749e7f081909c8196898c4191ad |
completed | May 3, 2026, 5:04 a.m. |
Created at: May 1, 2026, 1:23 a.m.