Triple
T19677957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Right and the Good |
E472504
|
entity |
| Predicate | listsPrimaFacieDutyType |
P445
|
FINISHED |
| Object | fidelity |
—
|
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: fidelity | Statement: [The Right and the Good, listsPrimaFacieDutyType, fidelity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: listsPrimaFacieDutyType Context triple: [The Right and the Good, listsPrimaFacieDutyType, fidelity]
-
A.
obligationType
chosen
Indicates the specific kind or category of duty, requirement, or commitment that applies within an obligation relationship.
-
B.
hasDutiesUnder
Indicates that one party is obligated to perform specific responsibilities or fulfill obligations as defined by another party, agreement, or authority.
-
C.
taskType
Indicates the specific category or kind of task an action or assignment belongs to within a broader set of tasks.
-
D.
mayHaveDuties
Indicates that an entity is potentially subject to certain responsibilities, tasks, or obligations, without asserting that these duties necessarily exist.
-
E.
dutyRecognized
Indicates that an obligation or responsibility has been acknowledged or accepted by the relevant party.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bceef881909c5b655af709c8c6 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.