Triple
T873880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rigveda |
E18873
|
entity |
| Predicate | composedInRegion |
P8263
|
FINISHED |
| Object | northwestern Indian subcontinent |
—
|
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: northwestern Indian subcontinent | Statement: [Rigveda, composedInRegion, northwestern Indian subcontinent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: composedInRegion Context triple: [Rigveda, composedInRegion, northwestern Indian subcontinent]
-
A.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
-
B.
usedInRegion
Indicates that something is utilized or applied within a specific geographic or administrative region.
-
C.
emergedInRegion
chosen
Indicates that something first appeared, originated, or came into existence within a specified geographic region.
-
D.
coreRegionOf
Indicates that one entity constitutes the central or most essential part of another entity’s structure, area, or domain.
-
E.
composedBy
Indicates that one entity is the creator or author of a musical or artistic work associated with 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac992d8c819088800f5a713fa7a4 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.