Triple
T17962110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anarta |
E449109
|
entity |
| Predicate | geographicallyOverlaps |
P93335
|
FINISHED |
| Object | modern Gujarat |
—
|
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: modern Gujarat | Statement: [Anarta, geographicallyOverlaps, modern Gujarat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicallyOverlaps Context triple: [Anarta, geographicallyOverlaps, modern Gujarat]
-
A.
geographicOverlap
chosen
Indicates that two geographic areas share at least part of the same physical space or territory.
-
B.
containsGeographicalArea
Indicates that one geographical area spatially encompasses or includes another geographical area within its boundaries.
-
C.
presentDayAdministrativeAreaOverlap
Indicates that two entities share a common geographic area within their current official administrative boundaries.
-
D.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
E.
arealRelation
Indicates a spatial relationship between areas, such as overlap, containment, adjacency, or relative positioning between two regions.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b132cc10819088526a0b4b098d69 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.