Triple
T6384233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore's paradox |
E143658
|
entity |
| Predicate | pragmaticStatus |
P70305
|
FINISHED |
| Object | pragmatically absurd |
—
|
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: pragmatically absurd | Statement: [Moore's paradox, pragmaticStatus, pragmatically absurd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pragmaticStatus Context triple: [Moore's paradox, pragmaticStatus, pragmatically absurd]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
deFactoStatus
Indicates that one entity holds a role, position, or status in practice or by custom, even if it is not formally or legally recognized.
-
C.
nominalStatus
Indicates that an entity holds a particular title, label, or status in name or designation, without necessarily implying associated functions or actions.
-
D.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
-
E.
approvalStatus
Indicates the current state of authorization or acceptance granted to an entity or action.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06856434481909cbbca1c12c6e070 |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:34 p.m.