Triple
T4664510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhils |
E102811
|
entity |
| Predicate | historicallyMentionedIn |
P8083
|
FINISHED |
| Object | ancient Indian texts and epics |
—
|
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: ancient Indian texts and epics | Statement: [Bhils, historicallyMentionedIn, ancient Indian texts and epics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyMentionedIn Context triple: [Bhils, historicallyMentionedIn, ancient Indian texts and epics]
-
A.
historicalReference
chosen
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
B.
historicallyIn
Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
-
C.
historicallyLinked
Indicates that two entities are connected through a shared or related historical event, period, or development.
-
D.
historicallySpoke
Indicates that an entity used a particular language as a spoken language during some period in the past.
-
E.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
- 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_69bd43d9cba4819086c1ab1c2d9d2133 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd655aceb081908100ffc0498fe183 |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6215864c8190b50ba0f63ba87d0c |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.