Triple
T34761523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BQP vs. the Polynomial Hierarchy |
E1002076
|
entity |
| Predicate | concernsClass |
P183764
|
FINISHED |
| Object | BQP |
—
|
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: BQP | Statement: [BQP vs. the Polynomial Hierarchy, concernsClass, BQP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsClass Context triple: [BQP vs. the Polynomial Hierarchy, concernsClass, BQP]
-
A.
concernsFunction
Indicates that something is related to, involves, or pertains to a particular function or functional aspect.
-
B.
concernsRule
Indicates that something is related or pertains specifically to a particular rule.
-
C.
concernsClause
Indicates that one entity (such as a document, statement, or discussion) is about, relates to, or addresses a particular clause.
-
D.
concernsEntity
Indicates that something (such as an action, issue, or piece of information) is about or relevant to a particular entity.
-
E.
concernsView
Indicates that one entity is about, relates to, or is focused on a particular view, perspective, or way of seeing something.
- 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_69f76db0fb30819096709d43f9a1f45f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7a283388c81908e4a9ee3369e8d6f |
completed | May 3, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a224365081908ff6958e3b30bd05 |
completed | May 3, 2026, 7:29 p.m. |
Created at: May 3, 2026, 3:59 p.m.