Triple
T30407242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | renBCH |
E773511
|
entity |
| Predicate | chainType |
P70534
|
FINISHED |
| Object | Ethereum mainnet |
—
|
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: Ethereum mainnet | Statement: [renBCH, chainType, Ethereum mainnet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chainType Context triple: [renBCH, chainType, Ethereum mainnet]
-
A.
chain
Indicates that one entity is linked or connected in sequence to another, typically as part of a series or chain of related elements or actions.
-
B.
chains
Indicates that one entity is physically or metaphorically bound, linked, or restrained by another through chains or a chain-like connection.
-
C.
chainCharacteristic
chosen
Indicates that one entity specifies a characteristic, property, or attribute of a chain associated with another entity.
-
D.
chainSymbolizes
Indicates that one entity serves as a symbolic representation or emblem of another within a chain or sequence of related symbols.
-
E.
chainPosition
Indicates the position or rank an entity occupies within an ordered chain or sequence relative to other entities.
- 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_69f22490b8b48190ab10c886a8d58c89 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:04 p.m.