Triple
T4738600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purusha Sukta |
E105183
|
entity |
| Predicate | hasAlternateVerseCount |
P8730
|
FINISHED |
| Object | 24 verses (extended recension) |
—
|
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: 24 verses (extended recension) | Statement: [Purusha Sukta, hasAlternateVerseCount, 24 verses (extended recension)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateVerseCount Context triple: [Purusha Sukta, hasAlternateVerseCount, 24 verses (extended recension)]
-
A.
hasVerseCount
chosen
Indicates that an entity (such as a text or section) is associated with a specific number of verses it contains.
-
B.
hasMultipleVerses
Indicates that something, typically a song, poem, or text, consists of more than one verse.
-
C.
hasVersesBy
Indicates a relationship where a work, such as a song or poem, contains verses authored or written by a specific creator.
-
D.
hasAlternativeVocalization
Indicates that an entity has another valid way it can be vocalized or pronounced, distinct from its primary or standard vocalization.
-
E.
approximateNumberOfVerses
Indicates an estimated or approximate count of verses associated with an entity.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6485d690819098dc4a974516da6b |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.