Triple
T38299846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mysore silk |
E1032191
|
entity |
| Predicate | hasStateOfOrigin |
P193134
|
FINISHED |
| Object | Karnataka |
—
|
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: Karnataka | Statement: [Mysore silk, hasStateOfOrigin, Karnataka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateOfOrigin Context triple: [Mysore silk, hasStateOfOrigin, Karnataka]
-
A.
primaryOriginState
Indicates the state that serves as the main or original source location associated with an entity.
-
B.
hasSettingOfOrigin
Indicates that something originates from, or was initially set in, a particular setting or environment.
-
C.
hasTypicalGeographicOrigin
Indicates that an entity is commonly or characteristically associated with originating from a particular geographic location.
-
D.
administrativeRegionOfOrigin
chosen
Indicates the administrative region (such as a state, province, or similar division) from which an entity originates or is associated by origin.
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00b3d2e0c88190a8bf49576e654f64 |
completed | May 10, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_6a00b376f4e48190a6676779fe02ea9f |
completed | May 10, 2026, 4:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.