Triple
T1685996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form of the Good |
E36441
|
entity |
| Predicate | axiologicalPriority |
P7594
|
FINISHED |
| Object | supreme standard of value |
—
|
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: supreme standard of value | Statement: [Form of the Good, axiologicalPriority, supreme standard of value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: axiologicalPriority Context triple: [Form of the Good, axiologicalPriority, supreme standard of value]
-
A.
primaryCriterion
chosen
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
B.
primacyOfHonorOver
Indicates that one entity is regarded as having higher honor, status, or precedence than another.
-
C.
primaryAlignment
Indicates the main or most significant way in which one entity is aligned, associated, or in agreement with another entity, standard, or category.
-
D.
aimsToBalance
Indicates an intention or effort by one entity to bring multiple elements, forces, or conditions into a state of equilibrium.
-
E.
missionPriority
Indicates the relative level of importance or urgency assigned to a mission compared to other missions or tasks.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.