Triple
T3064238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block 1 |
E62064
|
entity |
| Predicate | successorConfiguration |
P44183
|
FINISHED |
| Object | Block 1B |
—
|
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: Block 1B | Statement: [Block 1, successorConfiguration, Block 1B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorConfiguration Context triple: [Block 1, successorConfiguration, Block 1B]
-
A.
successorState
Indicates that one state directly follows another as the immediate next state in a sequence or process.
-
B.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
C.
successorModel
Indicates that one model is the direct follow-up or replacement for another earlier model.
-
D.
successorInPractice
Indicates that one entity has taken over the role, position, or function of another in actual practice, even if not formally or officially designated as its successor.
-
E.
successorUse
Indicates that one entity is used or applied as the subsequent or follow-up use of another entity in a sequence or lifecycle.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea2154c8190ab243feb77170a15 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97f7630c81908e1ca8a69611cff6 |
completed | March 8, 2026, 3:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.