Triple
T15507258
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kvasir |
E379113
|
entity |
| Predicate | wisdomType |
P22421
|
FINISHED |
| Object | universal knowledge |
—
|
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: universal knowledge | Statement: [Kvasir, wisdomType, universal knowledge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wisdomType Context triple: [Kvasir, wisdomType, universal knowledge]
-
A.
relativeWisdomDescription
Indicates a comparative assessment of wisdom between entities, describing how one’s wisdom level relates to another’s.
-
B.
typeOfIntelligence
Indicates that one entity is a specific kind or category of intelligence in relation to another entity.
-
C.
typeOfSpirit
Indicates the specific kind or category of spirit (e.g., ghost, demon, angel) that an entity belongs to.
-
D.
languagePhilosophyType
Indicates a relationship where a particular philosophy is categorized or characterized by a specific type or school within the philosophy of language.
-
E.
knowledgeType
chosen
Indicates the specific category or nature of knowledge associated with an entity or statement (e.g., factual, procedural, conceptual).
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcea8888190a7b69aca360183c3 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:55 a.m.