Triple
T22538429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purandara Dasa |
E557217
|
entity |
| Predicate | approximateNumberOfCompositionsAttributed |
P146519
|
FINISHED |
| Object | thousands |
—
|
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: thousands | Statement: [Purandara Dasa, approximateNumberOfCompositionsAttributed, thousands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateNumberOfCompositionsAttributed Context triple: [Purandara Dasa, approximateNumberOfCompositionsAttributed, thousands]
-
A.
opusNumberOfComposer
Indicates that a specific opus number is assigned to the works of a particular composer.
-
B.
approximateNumberOfWorks
chosen
Indicates an estimated or roughly calculated count of works associated with an entity.
-
C.
circaComposition
Indicates that one entity was composed or created around, but not exactly on, the time associated with another entity.
-
D.
numberOfWorksCreated
Indicates the total count of creative works that an entity has produced or authored.
-
E.
notableComposition
Indicates that an entity is a significant or well-known work created by another entity, such as a notable musical, literary, or artistic composition.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f302cd4819098c97ca4fa96363e |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.