Triple
T24999896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramtek |
E625688
|
entity |
| Predicate | namedInLiterature |
P117184
|
FINISHED |
| Object | associated with poet Kalidasa |
—
|
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: associated with poet Kalidasa | Statement: [Ramtek, namedInLiterature, associated with poet Kalidasa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedInLiterature Context triple: [Ramtek, namedInLiterature, associated with poet Kalidasa]
-
A.
nameInLiterature
chosen
Indicates that a particular name is used or appears for an entity within a literary work or context.
-
B.
hasReputationInLiterature
Indicates that an entity is recognized or regarded in a particular way within literary works or the field of literature.
-
C.
hasLiterarySignificance
Indicates that something holds notable importance, influence, or value within the realm of literature or literary studies.
-
D.
namedInHistoricalSources
Indicates that an entity is explicitly mentioned or identified in historical documents or records.
-
E.
attestedInWorksOf
Indicates that something (such as a claim, form, or usage) is documented or evidenced within the works produced by a particular author or creator.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0b35048190ae886a4fd5d385a7 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:04 a.m.