Triple
T26966673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | typicalAcceptanceCondition |
P199308
|
FINISHED |
| Object | yes-instances accepted with probability at least 2/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: yes-instances accepted with probability at least 2/3 | Statement: [BPP, typicalAcceptanceCondition, yes-instances accepted with probability at least 2/3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAcceptanceCondition Context triple: [BPP, typicalAcceptanceCondition, yes-instances accepted with probability at least 2/3]
-
A.
acceptanceCondition
Indicates the criteria or circumstances under which something is approved, agreed to, or deemed valid.
-
B.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
C.
typicalTrackCondition
Indicates the usual or standard state or quality of a track under normal conditions.
-
D.
hasTypicalConditions
Indicates that something is associated with conditions or circumstances that are commonly or normally present for it.
-
E.
mandatedAcceptanceOf
Indicates that one entity is required, by rule or authority, to accept or approve something from another entity.
- 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff2eb19ad88190915fbbe08e8bc84e |
completed | May 9, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69ff2db5dd608190b7b7ba95f19c276c |
completed | May 9, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69ff2eb0c0888190b0e05a03bf06d388 |
completed | May 9, 2026, 12:55 p.m. |
Created at: April 27, 2026, 6:36 a.m.