Triple
T25489686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesara style |
E638804
|
entity |
| Predicate | prominentAt |
P136851
|
FINISHED |
| Object | Pattadakal |
—
|
NE NERFINISHED |
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: Pattadakal | Statement: [Vesara style, prominentAt, Pattadakal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentAt Context triple: [Vesara style, prominentAt, Pattadakal]
-
A.
hasProminence
Indicates that one entity stands out in importance, visibility, or influence relative to others within a given context.
-
B.
isOneOfMostProminentIn
chosen
Indicates that an entity ranks among the most notable, influential, or widely recognized members within a specified group, category, or domain.
-
C.
wasProminent
Indicates that an entity held a position of significant importance, influence, or visibility within a particular context or period.
-
D.
isMostProminentIn
Indicates that an entity stands out as the most notable, influential, or dominant among comparable entities within a specified context or domain.
-
E.
unitOfProminence
Indicates that one entity specifies the unit or scale in which the prominence or significance of another entity is measured or expressed.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7a4658081908758aa293923090d |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 2:34 p.m.