Triple
T693658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | categorical imperative |
E13849
|
entity |
| Predicate | presupposes |
P14814
|
FINISHED |
| Object | rational agency |
—
|
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: rational agency | Statement: [categorical imperative, presupposes, rational agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presupposes Context triple: [categorical imperative, presupposes, rational agency]
-
A.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
B.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
C.
precondition
chosen
Indicates that one event, state, or condition must be true or occur before another event, state, or condition can validly or successfully take place.
-
D.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
E.
imposes
Indicates that one entity enforces, applies, or places a rule, condition, burden, or obligation upon another 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0b1e1d08190bdd42f57be5c2a6b |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d23e0a08190b08be9d1eff2a1bb |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.