Triple
T7062657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakrat |
E164256
|
entity |
| Predicate | regionalNameIn |
P14444
|
FINISHED |
| Object | parts of India |
—
|
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: parts of India | Statement: [Sakrat, regionalNameIn, parts of India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionalNameIn Context triple: [Sakrat, regionalNameIn, parts of India]
-
A.
hasRegionalName
Indicates that an entity is known by a specific name or designation within a particular region or locality.
-
B.
regionName
Indicates the name assigned to a specific geographic or administrative region.
-
C.
nameDayRegion
Indicates the region or geographic area in which a particular name day is observed or recognized.
-
D.
regionallyKnownAs
chosen
Indicates that an entity is known by a particular name or designation within a specific geographic region.
-
E.
regionNamedAfter
Indicates that a geographic region derives its name from a specific person, place, event, or other entity.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e4a3c36c819080942c59f1830ae8 |
completed | March 27, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69c6e1bdc1f08190975fcdbbb1854d1e |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:38 p.m.