Triple
T4906912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dvaraka Sharada Peetham |
E109932
|
entity |
| Predicate | traditionallyEstablished |
P31438
|
FINISHED |
| Object | 8th century |
—
|
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: 8th century | Statement: [Dvaraka Sharada Peetham, traditionallyEstablished, 8th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyEstablished Context triple: [Dvaraka Sharada Peetham, traditionallyEstablished, 8th century]
-
A.
traditionallyDated
chosen
Indicates that something is assigned a date based on traditional or customary chronology rather than on firmly established historical or scientific evidence.
-
B.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
-
C.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
D.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
E.
traditionallyLivedTo
Indicates that an entity customarily or historically resided in a particular place or environment over an extended 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e7452d481909078a0027e2a4566 |
completed | March 20, 2026, 3:57 p.m. |
| PD | Predicate disambiguation | batch_69bd6c325e188190823836d79934e9bc |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.