Triple
T38661104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upatiṣya |
E940333
|
entity |
| Predicate | hasPrimaryQuality |
P80525
|
FINISHED |
| Object | paññā (wisdom) |
—
|
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: paññā (wisdom) | Statement: [Upatiṣya, hasPrimaryQuality, paññā (wisdom)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryQuality Context triple: [Upatiṣya, hasPrimaryQuality, paññā (wisdom)]
-
A.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
B.
hasPrimaryFeature
chosen
Indicates that an entity possesses a main or most characteristic feature that defines or distinguishes it.
-
C.
hasPrimarySee
Indicates that one entity is designated as the main or preferred "see" reference or cross-reference for another entity.
-
D.
hasPrimarySubject
Indicates that an entity is the main or principal subject associated with another entity or resource.
-
E.
hasQualityCriterion
Indicates that something is associated with a specific standard or criterion used to judge its quality.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.