Triple
T18399112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anushtubh meter |
E449943
|
entity |
| Predicate | hasCanonicalLength |
P130970
|
FINISHED |
| Object | 32-syllable stanza |
—
|
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: 32-syllable stanza | Statement: [Anushtubh meter, hasCanonicalLength, 32-syllable stanza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalLength Context triple: [Anushtubh meter, hasCanonicalLength, 32-syllable stanza]
-
A.
hasCanonicalRepresentation
Indicates that one entity is the standard or authoritative form in which another entity is represented.
-
B.
hasCanonicalNumber
Indicates that an entity is associated with its officially recognized or standard reference number.
-
C.
hasCanonicalCharacter
Indicates that something is associated with or defined by its standard, officially recognized character representation.
-
D.
hasCanonicalReference
Indicates that one entity serves as the authoritative or standard reference source for another entity.
-
E.
hasCanonicalTerm
Indicates that one term in a set is designated as the standard or authoritative form used to represent a concept or 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_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.