Triple
T4882273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angiras sages |
E109356
|
entity |
| Predicate | ethnicCulturalContext |
P56388
|
FINISHED |
| Object | Indo-Aryan |
—
|
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: Indo-Aryan | Statement: [Angiras sages, ethnicCulturalContext, Indo-Aryan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicCulturalContext Context triple: [Angiras sages, ethnicCulturalContext, Indo-Aryan]
-
A.
ethnicAspect
Indicates a relationship where one entity reflects, involves, or characterizes the ethnic background, identity, or attributes of another entity.
-
B.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
C.
culturalRegion
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
D.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
E.
culturalVariation
Indicates that there are differences in practices, beliefs, or expressions between cultures or within a culture across groups, contexts, or time.
- 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_69bd440e9d64819083e82cf33b4d9570 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6dde6fcc8190a5aa7587f85632bd |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2be5e881909f6ec9c3bcde49f3 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.