Triple
T24040350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chakravartin |
E595354
|
entity |
| Predicate | idealQuality |
P154631
|
FINISHED |
| Object | moral perfection |
—
|
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: moral perfection | Statement: [Chakravartin, idealQuality, moral perfection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: idealQuality Context triple: [Chakravartin, idealQuality, moral perfection]
-
A.
quality
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
-
B.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
C.
hasIdeal
Indicates that an entity holds or is associated with a guiding principle, standard, or value it considers perfect or most desirable.
-
D.
coreIdeal
Indicates that something is a fundamental, central principle or value that defines or strongly guides another entity.
-
E.
storageQuality
Indicates the degree or standard of how well something is stored, such as its preservation, safety, or suitability for use.
- F. None of above. chosen
Provenance (4 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d8d8b7248190a4e7f152d6bfc2bc |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 9:57 p.m.