Triple
T31713095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BWR-3 |
E809379
|
entity |
| Predicate | generationSuccessor |
P31540
|
FINISHED |
| Object | BWR-4 |
—
|
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: BWR-4 | Statement: [BWR-3, generationSuccessor, BWR-4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generationSuccessor Context triple: [BWR-3, generationSuccessor, BWR-4]
-
A.
successorFrom
Indicates that one entity directly follows or comes after another in an ordered sequence or progression.
-
B.
successorFunction
Indicates the relationship where one entity is defined as the immediate next or following element in a sequence or ordered set relative to another.
-
C.
successorPopulation
Indicates that one population directly follows or replaces another population in a temporal or sequential order.
-
D.
successorCoreGeneration
chosen
Indicates that one generation directly follows and replaces another as its core or primary generation in a sequence or lineage.
-
E.
successorChild
Indicates that one entity is the child of another entity who is its immediate predecessor or predecessor in a succession or lineage.
- 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_69f6aaf50be08190a2b62a6d881f8aee |
completed | May 3, 2026, 1:55 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:16 p.m.