Triple
T18399104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anushtubh meter |
E449943
|
entity |
| Predicate | hasCommonForm |
P169
|
FINISHED |
| Object | 4x8-syllable shloka form |
—
|
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: 4x8-syllable shloka form | Statement: [Anushtubh meter, hasCommonForm, 4x8-syllable shloka form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonForm Context triple: [Anushtubh meter, hasCommonForm, 4x8-syllable shloka form]
-
A.
hasForm
chosen
Indicates that one entity possesses, exhibits, or is characterized by a particular shape, structure, or configuration.
-
B.
hasFullForm
Indicates that one entity is the complete, expanded, or unabbreviated form of another entity.
-
C.
hasComponentForm
Indicates that one entity exists as a structural or compositional form or variant of another entity.
-
D.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
E.
hasFormFor
Indicates that one entity possesses or provides a specific form or document intended to be used by another entity or for a particular purpose.
- 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_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. |
Created at: April 10, 2026, 10:46 a.m.