Triple
T29837472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INCOC |
E757692
|
entity |
| Predicate | associatedStateOrRegion |
P61858
|
FINISHED |
| Object | Kerala |
E34853
|
NE 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: Kerala | Statement: [INCOC, associatedStateOrRegion, Kerala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStateOrRegion Context triple: [INCOC, associatedStateOrRegion, Kerala]
-
A.
associatedProvinceOrState
Indicates that one entity is linked or related to a specific province or state as its relevant administrative region.
-
B.
stateOrRegion
Indicates that one entity is a state or region in which the other entity is located or with which it is associated.
-
C.
regionOfState
Indicates that one administrative or geographical region is a subdivision or part of a larger state.
-
D.
associatedAdministrativeRegion
chosen
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
E.
associatedStateCapitalRegion
Indicates that a state is linked to the capital region that serves as its primary administrative or governmental center.
- F. None of above.
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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26f1ad976c819085a59a20b650a1f6 |
completed | June 8, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:37 p.m.