Triple
T13892408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravens paradox |
E334006
|
entity |
| Predicate | usesLogicalForm |
P96516
|
FINISHED |
| Object | All R are B |
—
|
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: All R are B | Statement: [Ravens paradox, usesLogicalForm, All R are B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLogicalForm Context triple: [Ravens paradox, usesLogicalForm, All R are B]
-
A.
logicalForm
Indicates a relationship where an expression is associated with its structured, formal logical representation.
-
B.
hasLogicalStructure
Indicates that one entity possesses or exhibits a specific underlying logical organization or pattern defined by another entity.
-
C.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
-
D.
isFormulatedUsing
chosen
Indicates that something is created, defined, or expressed by means of a specified method, material, or set of components.
-
E.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
- 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_69d81c5dd2d48190b7a5fc1e009de936 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de23a537d4819093c2bae2a244816a |
completed | April 14, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69dd464b1ab48190ae50bfc902bf6ef7 |
completed | April 13, 2026, 7:38 p.m. |
Created at: April 9, 2026, 10:15 p.m.