Triple
T27308098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhatarka |
E689121
|
entity |
| Predicate | powerBaseLocation |
P60205
|
FINISHED |
| Object | present-day 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: present-day Gujarat | Statement: [Bhatarka, powerBaseLocation, present-day Gujarat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerBaseLocation Context triple: [Bhatarka, powerBaseLocation, present-day Gujarat]
-
A.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
B.
baseLocation
chosen
Indicates the primary place where an entity is based, headquartered, or operates from as its main location.
-
C.
hasPowerBase
Indicates that an entity derives support, influence, or authority from a particular group, location, or resource that serves as its primary base of power.
-
D.
positionRelativeToPower
Indicates the spatial or structural placement of one entity in relation to a power source, power line, or power-related infrastructure.
-
E.
powerPosition
Indicates that one entity holds a position of authority, control, or dominance over another within a hierarchy or power structure.
- 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_69ef355b931c8190a63cafaf7bcc008b |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 11:26 a.m.