Triple
T4816644
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Āraṇyaka |
E107604
|
entity |
| Predicate | traditionalSetting |
P39309
|
FINISHED |
| Object | forest |
—
|
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: forest | Statement: [Āraṇyaka, traditionalSetting, forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalSetting Context triple: [Āraṇyaka, traditionalSetting, forest]
-
A.
settingTraditional
chosen
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
B.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
C.
traditionalStart
Indicates that an event, process, or sequence begins in the customary or historically established way.
-
D.
traditionalKit
Indicates that an entity is a conventional or customary set of tools, equipment, or components used together for a particular purpose.
-
E.
traditionalStatus
Indicates that one entity holds a customary, long-established, or culturally recognized role, condition, or standing in relation to 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:23 p.m.