Triple
T7483598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandragupta II |
E176823
|
entity |
| Predicate | expandedToRegion |
P18876
|
FINISHED |
| Object | western 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: western India | Statement: [Chandragupta II, expandedToRegion, western India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedToRegion Context triple: [Chandragupta II, expandedToRegion, western India]
-
A.
expansionRegion
Indicates a region or area into which something (such as a structure, process, or influence) is intended or allowed to expand.
-
B.
expandedAs
Indicates that one entity is a more detailed, elaborated, or fully written-out form of another, capturing how the latter is expanded from the former.
-
C.
expandedTerritoryTo
chosen
Indicates that one entity has increased the geographic area under its control or influence to include the territory of another entity.
-
D.
expandedBy
Indicates that one entity increases, elaborates, or builds upon the scope, detail, or extent of another entity.
-
E.
expandedRuleTo
Indicates that one rule has been broadened, elaborated, or transformed into another, more detailed or extensive rule.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f53923e4819081bf79ed962a971c |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.