Triple
T21355008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vālmīki |
E526594
|
entity |
| Predicate | associatedWithMeter |
P143964
|
FINISHED |
| Object | shloka |
—
|
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: shloka | Statement: [Vālmīki, associatedWithMeter, shloka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMeter Context triple: [Vālmīki, associatedWithMeter, shloka]
-
A.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
associatedWithCharge
Indicates a relationship where an entity is linked to, involved in, or connected with a specific charge or accusation.
-
C.
associatedWithMode
Indicates a relationship in which something is linked or connected to a particular mode, method, or manner of operation or behavior.
-
D.
associatedWithUse
Indicates a relationship where one entity is connected to or involved in the use or utilization of another entity.
-
E.
associatedWithStandard
Indicates that something is linked or connected to a specific standard, such as being defined, governed, or guided by that standard.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8af9be3a48190aa8e6e9a5b812981 |
completed | April 22, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69e6162bbfc88190a3e75859941b2638 |
completed | April 20, 2026, 12:03 p.m. |
| PDg | Predicate description generation | batch_69e61b3e47f881908fb2aac9bd2bfb58 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 16, 2026, 5:06 p.m.