Triple
T29152060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vatapi |
E738935
|
entity |
| Predicate | hasNearbySites |
P19575
|
FINISHED |
| Object | Aihole |
—
|
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: Aihole | Statement: [Vatapi, hasNearbySites, Aihole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySites Context triple: [Vatapi, hasNearbySites, Aihole]
-
A.
hasNearbySiteType
Indicates that one entity has another entity of a specified site type located in its close physical vicinity.
-
B.
nearbySitePartOf
Indicates that one site or site component is located close to and is considered part of another, larger site or site component.
-
C.
refersToNearbySite
Indicates that one entity makes reference to another site or location that is geographically close or adjacent.
-
D.
hasNearbySitePeriod
Indicates that a site has an associated historical or temporal period that is geographically nearby or closely related in location.
-
E.
notableNearbySite
chosen
Indicates that one entity is a significant or noteworthy site located close to another entity.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe00dad1708190b6522476bebb43af |
completed | May 8, 2026, 3:27 p.m. |
| PD | Predicate disambiguation | batch_69fdfc3717f48190bb50ac2919c8ef95 |
completed | May 8, 2026, 3:07 p.m. |
Created at: April 28, 2026, 11:42 a.m.