Triple
T26966674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | typicalRejectionCondition |
P161386
|
FINISHED |
| Object | no-instances accepted with probability at most 1/3 |
—
|
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: no-instances accepted with probability at most 1/3 | Statement: [BPP, typicalRejectionCondition, no-instances accepted with probability at most 1/3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRejectionCondition Context triple: [BPP, typicalRejectionCondition, no-instances accepted with probability at most 1/3]
-
A.
rejectionCondition
chosen
Indicates the condition or set of criteria under which something (such as a request, offer, or item) is deemed unacceptable and therefore refused or discarded.
-
B.
typicalAcceptanceCondition
Indicates the usual or standard conditions under which something is accepted or deemed acceptable.
-
C.
rejectionErrorType
Indicates the specific category or nature of the error that caused a rejection to occur.
-
D.
rejectedRequirement
Indicates that a proposed requirement has been evaluated and explicitly not accepted or approved.
-
E.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: April 27, 2026, 6:36 a.m.