Triple
T30407251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | renBCH |
E773511
|
entity |
| Predicate | bridgeMechanism |
P106503
|
FINISHED |
| Object | RenVM darknodes |
—
|
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: RenVM darknodes | Statement: [renBCH, bridgeMechanism, RenVM darknodes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeMechanism Context triple: [renBCH, bridgeMechanism, RenVM darknodes]
-
A.
bridgeLocation
Indicates the specific place or area where a bridge is situated or spans.
-
B.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
C.
bridgeComponent
chosen
Indicates that one entity functions as a structural or functional component of a bridge associated with another entity.
-
D.
bridgeModel
Indicates a relationship where one entity serves as an intermediate model or representation that connects or translates between two other entities or systems.
-
E.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
- 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_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:04 p.m.