Triple
T31645232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arabhi |
E807567
|
entity |
| Predicate | usesPanchama |
P181772
|
FINISHED |
| Object | P |
—
|
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: P | Statement: [Arabhi, usesPanchama, P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPanchama Context triple: [Arabhi, usesPanchama, P]
-
A.
isPancharangaKshetram
Indicates that a temple or sacred site is recognized as one of the Pancharanga Kshetrams, the five traditional holy shrines dedicated to Lord Ranganatha (Vishnu) along the Kaveri river.
-
B.
hasChhatri
Indicates that one entity possesses or features a chhatri (a dome-shaped pavilion or canopy structure) in relation to another entity or location.
-
C.
isUpapandava
Indicates that one entity is an Upapandava, i.e., a son or secondary descendant of the Pandavas, in relation to a specified context or lineage.
-
D.
usesKomalRe
Indicates that one entity employs or incorporates the musical note Komal Re (flattened second) in relation to another entity or context.
-
E.
hasTheka
Indicates a relationship where one entity possesses, is equipped with, or features a theka (a specific rhythmic pattern or accompaniment).
- F. None of above. chosen
Provenance (4 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_69f348d9ce58819093ea2da83cbeeec1 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7824dc3f0819092a5102895b4a478 |
completed | May 3, 2026, 5:13 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
| PDg | Predicate description generation | batch_69f7817c79e081908e685c48165e086b |
completed | May 3, 2026, 5:10 p.m. |
Created at: April 30, 2026, 10:50 p.m.