Triple
T26966686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | relationshipToNP |
P198916
|
FINISHED |
| Object | unknown whether NP ⊆ 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: unknown whether NP ⊆ BPP | Statement: [BPP, relationshipToNP, unknown whether NP ⊆ BPP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToNP Context triple: [BPP, relationshipToNP, unknown whether NP ⊆ BPP]
-
A.
relationshipStatusWithNP
chosen
Indicates the type or state of a relationship that one entity has with a specified noun phrase (NP).
-
B.
relationshipToNPC
Indicates the type of interpersonal or narrative connection that one entity has with a non-player character (NPC).
-
C.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
- 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_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: April 27, 2026, 6:36 a.m.