Triple
T26735785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mound RGR-8 |
E674104
|
entity |
| Predicate | siteComplexComponent |
P5003
|
FINISHED |
| Object | RGR-1 to RGR-9 mounds at Rakhigarhi |
—
|
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: RGR-1 to RGR-9 mounds at Rakhigarhi | Statement: [Mound RGR-8, siteComplexComponent, RGR-1 to RGR-9 mounds at Rakhigarhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siteComplexComponent Context triple: [Mound RGR-8, siteComplexComponent, RGR-1 to RGR-9 mounds at Rakhigarhi]
-
A.
siteManager
Indicates that an entity is responsible for managing, overseeing, or administering a particular site or location.
-
B.
containsSite
chosen
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
integrationSite
Indicates the specific location or context where one entity is incorporated or embedded into another.
-
D.
typeSite
Indicates that a site is classified as being of a particular type or category.
-
E.
site
Indicates that one entity is the physical or virtual location where another entity is situated, occurs, or is based.
- 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61844d7f8819081080f687999b77a |
completed | May 2, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:47 a.m.