Triple
T31631394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Koothattukulam |
E807175
|
entity |
| Predicate | hasAgrarianSurroundings |
P86124
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Koothattukulam, hasAgrarianSurroundings, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgrarianSurroundings Context triple: [Koothattukulam, hasAgrarianSurroundings, true]
-
A.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
B.
hasRuralLandscapeType
Indicates that an entity is associated with or characterized by a specific type of rural landscape.
-
C.
hasAgriculturalCommunities
Indicates that certain groups or settlements engage in organized farming and related agricultural activities within a given area or context.
-
D.
locatedInAgriculturalRegion
Indicates that an entity is situated within a region primarily characterized by agricultural activities or land use.
-
E.
agriculturalEnvironment
chosen
Indicates that something exists in, is associated with, or is influenced by an agricultural or farming-related environment.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8e5799c8190900640d78b1c5990 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a757c6e081908e37631e5d8d246b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:45 p.m.