Triple
T26966708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP |
E679190
|
entity |
| Predicate | relationToBPP |
P199054
|
FINISHED |
| Object | RP is a subset of BPP |
—
|
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: RP is a subset of BPP | Statement: [RP, relationToBPP, RP is a subset of BPP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationToBPP Context triple: [RP, relationToBPP, RP is a subset of BPP]
-
A.
relationToBabo
Indicates a relationship or connection that an entity has to the person or entity referred to as "Babo."
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationToITF
Indicates a relationship or association that an entity has with the ITF (International Tennis Federation), such as affiliation, governance, or regulatory connection.
-
D.
basisOfRelationship
Indicates that one entity serves as the foundational reason, cause, or justification for the relationship that exists between two or more entities.
-
E.
relationshipToParents
Indicates the type or nature of a person's familial relationship to their parents.
- 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_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: April 27, 2026, 6:36 a.m.