Triple
T5075561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hastinapura |
E114385
|
entity |
| Predicate | archaeologicalSiteNear |
P14422
|
FINISHED |
| Object | modern Hastinapur town |
—
|
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 Hastinapur town | Statement: [Hastinapura, archaeologicalSiteNear, modern Hastinapur town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: archaeologicalSiteNear Context triple: [Hastinapura, archaeologicalSiteNear, modern Hastinapur town]
-
A.
hasNearbyArchaeologicalSite
chosen
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
B.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
C.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
D.
notableNearbySite
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
E.
archaeologicalSiteIncludes
Indicates that an archaeological site contains, encompasses, or includes a specified feature, structure, artifact collection, or sub-area as part of its extent or composition.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.