Triple
T4762650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lavani |
E105731
|
entity |
| Predicate | primaryRhythmSource |
P59163
|
FINISHED |
| Object | dholki |
—
|
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: dholki | Statement: [Lavani, primaryRhythmSource, dholki]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRhythmSource Context triple: [Lavani, primaryRhythmSource, dholki]
-
A.
dominantExcitationSource
Indicates that one entity serves as the primary or most influential source of excitation affecting another entity or system.
-
B.
primaryGauge
Indicates that one gauge is designated as the main or principal measurement instrument among a set of gauges.
-
C.
primaryRegulator
Indicates that one entity serves as the main controlling or governing authority over another entity or process.
-
D.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
-
E.
primaryPower
Indicates that one entity serves as the main or dominant source of power or energy for another entity.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd686ef1b08190ad60375592c9d6c0 |
completed | March 20, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69bd622807f881908e4bcb14f7731bac |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd686dc7b88190b41e8a362701080d |
completed | March 20, 2026, 3:31 p.m. |
Created at: March 20, 2026, 1:20 p.m.