Triple
T33201478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srinivas |
E849909
|
entity |
| Predicate | primaryRegionOfFame |
P39809
|
FINISHED |
| Object | South India |
E31773
|
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: South India | Statement: [Srinivas, primaryRegionOfFame, South India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRegionOfFame Context triple: [Srinivas, primaryRegionOfFame, South India]
-
A.
primaryRegionOfPopularity
Indicates the geographic region where something is most widely used, favored, or popular compared to other regions.
-
B.
primaryRegionDepicted
Indicates that a resource primarily depicts or visually represents a particular geographic or spatial region as its main subject.
-
C.
primaryTerritory
Indicates that a specified area or region is the main or most important territory associated with an entity.
-
D.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
E.
regionallyAssociatedWith
Indicates that two entities are connected or related based on sharing the same or overlapping geographic or regional context.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fba63c88190b2bc3501bb2dac83 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.