Triple
T19548116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varadaraja Perumal |
E489127
|
entity |
| Predicate | holdsAttribute |
P136535
|
FINISHED |
| Object | shankha |
—
|
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: shankha | Statement: [Varadaraja Perumal, holdsAttribute, shankha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsAttribute Context triple: [Varadaraja Perumal, holdsAttribute, shankha]
-
A.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
B.
holdsAt
Indicates that a particular condition or fluent is true and persists at a specified point in time.
-
C.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
D.
holdsTo
Indicates that one entity maintains, adheres, or remains committed to another entity, such as a belief, standard, agreement, or condition.
-
E.
holdsFor
Indicates that a particular relationship or condition remains true over a specified interval or duration of time.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d2e5e588190ac3a6f612d4fb54b |
completed | April 20, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51796b4c48190b721114dde654bd7 |
completed | April 19, 2026, 5:57 p.m. |
Created at: April 10, 2026, 1:41 p.m.