Triple
T26306647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishnupad Temple, Gaya |
E661702
|
entity |
| Predicate | footprintEnshrinedIn |
P59560
|
FINISHED |
| Object | basalt rock |
—
|
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: basalt rock | Statement: [Vishnupad Temple, Gaya, footprintEnshrinedIn, basalt rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: footprintEnshrinedIn Context triple: [Vishnupad Temple, Gaya, footprintEnshrinedIn, basalt rock]
-
A.
enshrinedWithin
chosen
Indicates that one entity is formally preserved, honored, or safeguarded inside or as part of another entity, often with a sense of protection or reverence.
-
B.
enshrinedSince
Indicates that something has been formally established, preserved, or honored starting from a specific point in time.
-
C.
commemoratedIn
Indicates that something is honored, remembered, or recognized within a particular work, event, place, or medium.
-
D.
inscribedFor
Indicates that something is formally written, engraved, or dedicated for a particular recipient or purpose.
-
E.
inscribedUnder
Indicates that one entity is written, carved, or engraved beneath another entity, typically as a subordinate or accompanying inscription.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee3b22081909815d1ec423b02ae |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:19 p.m.