Triple
T4871192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rudraksha beads |
E109087
|
entity |
| Predicate | mostCommonMukhiRange |
P13474
|
FINISHED |
| Object | 1 to 14 |
—
|
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: 1 to 14 | Statement: [Rudraksha beads, mostCommonMukhiRange, 1 to 14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostCommonMukhiRange Context triple: [Rudraksha beads, mostCommonMukhiRange, 1 to 14]
-
A.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
numberOfCommonUseCharacters
Indicates the count of characters that are shared in common between two entities’ representations or strings.
-
C.
commonlyFrontedBy
Indicates that one element is typically placed at the beginning or in the leading position of another element.
-
D.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
E.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
- 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_69bd440d96a48190b0c87069adef2af1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c28e56081908ee411ac94c3769e |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:27 p.m.