Triple
T1106080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharma Chakra |
E25489
|
entity |
| Predicate | spokesSymbolize |
P129
|
FINISHED |
| Object | various virtues |
—
|
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: various virtues | Statement: [Dharma Chakra, spokesSymbolize, various virtues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokesSymbolize Context triple: [Dharma Chakra, spokesSymbolize, various virtues]
-
A.
mapSymbol
Indicates a correspondence where one symbol is used to represent, stand for, or denote another element within a mapping or representation system.
-
B.
routeSymbolShape
Indicates the specific geometric form or outline used to depict a route’s symbol in a visual or cartographic representation.
-
C.
coordinateSymbols
Indicates a relationship where one symbol is aligned or matched with another symbol in a coordinated or corresponding way.
-
D.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
E.
symbolicStyle
Indicates that one entity employs or is characterized by a particular symbolic or emblematic style defined by the other 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_69a49428d4448190b3b36991ceae87ce |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b9e339f88190afc027216e95d2f7 |
completed | March 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69a4b74877748190b78cd8847ee4fa7a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:43 p.m.