Triple
T31713096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-3 |
E809379
|
entity |
| Predicate | generationPredecessor |
P28897
|
FINISHED |
| Object | BWR-2 |
—
|
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: BWR-2 | Statement: [BWR-3, generationPredecessor, BWR-2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationPredecessor Context triple: [BWR-3, generationPredecessor, BWR-2]
-
A.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
B.
predecessorPopulation
chosen
Indicates that one population entity is the immediate prior version or state of another population entity in a temporal or evolutionary sequence.
-
C.
predecessorDesign
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
D.
predecessorFamily
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
E.
predecessorFunction
Indicates a function that maps each element to its immediate predecessor in an ordered sequence or structure.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:16 p.m.