Triple
T32789512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | law of excluded middle |
E838588
|
entity |
| Predicate | isRejectedIn |
P52534
|
FINISHED |
| Object | intuitionistic logic |
—
|
NE NERFINISHED |
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: intuitionistic logic | Statement: [law of excluded middle, isRejectedIn, intuitionistic logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRejectedIn Context triple: [law of excluded middle, isRejectedIn, intuitionistic logic]
-
A.
rejectedIn
chosen
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
B.
isProhibitedFor
Indicates that a certain action, object, or condition is not allowed or is forbidden for a specified entity or group.
-
C.
isDeniedBy
Indicates that a request, claim, or action directed at an entity is explicitly refused or rejected by another entity.
-
D.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
E.
canRejectWith
Indicates that one entity has the authority or ability to refuse, decline, or dismiss another entity or proposal using a specific method or condition.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:14 a.m.