Triple
T26966662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BPP |
E679189
|
entity |
| Predicate | conjecturedEqualTo |
P57009
|
FINISHED |
| Object | P |
—
|
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: P | Statement: [BPP, conjecturedEqualTo, P]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conjecturedEqualTo Context triple: [BPP, conjecturedEqualTo, P]
-
A.
mayBeEqualTo
chosen
Indicates that two entities are possibly equal, but their equality is uncertain or not definitively established.
-
B.
conjecturedSign
Indicates that one entity is proposed or hypothesized to be the sign, symbol, or indicator of another entity, without confirmed certainty.
-
C.
refinedConjecture
Indicates that a previously stated conjecture has been modified or made more precise, resulting in a refined version of the original conjecture.
-
D.
associatedConjecture
Indicates that one entity is linked or connected to a particular conjecture, typically as its subject, source, or relevant context.
-
E.
isEquiconsistentWith
Indicates that two formal theories or systems have the same consistency strength, such that if one is consistent then the other is also consistent, and if one is inconsistent then so is the other.
- 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_69f621210b788190ab9e910cd635f366 |
completed | May 2, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 6:36 a.m.