Triple
T15263792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Merge |
E364847
|
entity |
| Predicate | testingPredecessor |
P117851
|
FINISHED |
| Object | multiple testnet merges |
—
|
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: multiple testnet merges | Statement: [The Merge, testingPredecessor, multiple testnet merges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingPredecessor Context triple: [The Merge, testingPredecessor, multiple testnet merges]
-
A.
predecessorControl
Indicates that one entity has control or authority over another entity that precedes it in a sequence, process, or hierarchy.
-
B.
predecessorStatus
Indicates that one entity’s status is determined by, or directly follows from, the status of a preceding entity in a sequence or process.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
-
E.
predecessorResult
Indicates that one entity is the outcome or result produced by a preceding entity in a sequence or process.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.