Triple
T26800761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatsaraja |
E671092
|
entity |
| Predicate | expandedTerritoryTowards |
P18876
|
FINISHED |
| Object | Ganga-Yamuna doab |
—
|
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: Ganga-Yamuna doab | Statement: [Vatsaraja, expandedTerritoryTowards, Ganga-Yamuna doab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedTerritoryTowards Context triple: [Vatsaraja, expandedTerritoryTowards, Ganga-Yamuna doab]
-
A.
expandedTerritoryTo
chosen
Indicates that one entity has increased the geographic area under its control or influence to include the territory of another entity.
-
B.
expandedTerritoryOf
Indicates that one entity has increased or extended the geographic or jurisdictional area belonging to another entity.
-
C.
territorialExpansionDirection
Indicates the primary geographic direction in which an entity’s territory is expanding or has expanded.
-
D.
extendedTowards
Indicates that one entity is stretched or directed outward in the direction of another entity or location.
-
E.
expandedBeyondCountry
Indicates that an entity has grown or extended its operations, presence, or influence beyond the borders of its original country.
- 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 4:22 a.m.