Triple
T5336315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shakti Peetha |
E123834
|
entity |
| Predicate | numberTraditionallyCountedAs |
P20392
|
FINISHED |
| Object | 51 |
—
|
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: 51 | Statement: [Shakti Peetha, numberTraditionallyCountedAs, 51]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberTraditionallyCountedAs Context triple: [Shakti Peetha, numberTraditionallyCountedAs, 51]
-
A.
ordinalNumber
Indicates the position or rank of an entity within an ordered sequence (e.g., first, second, third).
-
B.
numberInClassicalTradition
chosen
Indicates that an entity is associated with a specific number as defined or used within a particular classical tradition (e.g., mythology, religion, or philosophy).
-
C.
numberOfCounts
Indicates the total quantity or tally of discrete occurrences, items, or instances associated with an entity or event.
-
D.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
E.
areCountedBy
Indicates that one entity serves as the counting mechanism, record, or process by which the quantity of another entity is determined.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85b104c081908b81236a0142e1c8 |
completed | March 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.