Triple
T18399213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anustubh |
E449945
|
entity |
| Predicate | hasNameInIAST |
P130972
|
FINISHED |
| Object | Anuṣṭubh |
—
|
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: Anuṣṭubh | Statement: [Anustubh, hasNameInIAST, Anuṣṭubh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInIAST Context triple: [Anustubh, hasNameInIAST, Anuṣṭubh]
-
A.
hasNameString
Indicates that an entity is associated with a specific textual string used as its name.
-
B.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
C.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
D.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
E.
hasNameInFormula
Indicates that an entity is referred to by a specific name or symbol within a formula or formal expression.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e518499b1481909c5de786c48faeba |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:46 a.m.