Triple
T26966682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | hasCompleteProblems |
P197475
|
FINISHED |
| Object | unknown under standard reductions |
—
|
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: unknown under standard reductions | Statement: [BPP, hasCompleteProblems, unknown under standard reductions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompleteProblems Context triple: [BPP, hasCompleteProblems, unknown under standard reductions]
-
A.
hasFirstSolvedProblem
Indicates that an entity is the first one to have successfully solved a particular problem.
-
B.
containsCompleteProblem
Indicates that one entity fully includes or encompasses an entire, self-contained problem associated with another entity.
-
C.
numberOfProblems
Indicates the quantity or count of problems associated with a given entity or situation.
-
D.
problemTypeSolved
Indicates that a given problem has been successfully solved or resolved by a particular entity or method.
-
E.
hasCompleted
Indicates that an entity has finished or successfully carried out a specified task, process, or activity.
- 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_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
| PDg | Predicate description generation | batch_69fe96c0b760819093737292d33df165 |
completed | May 9, 2026, 2:06 a.m. |
Created at: April 27, 2026, 6:36 a.m.