Triple
T30406925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binance Smart Chain |
E773504
|
entity |
| Predicate | bridgeAvailable |
P72280
|
FINISHED |
| Object | Binance Bridge |
—
|
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: Binance Bridge | Statement: [Binance Smart Chain, bridgeAvailable, Binance Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeAvailable Context triple: [Binance Smart Chain, bridgeAvailable, Binance Bridge]
-
A.
bridgeStatus
chosen
Indicates the current operational condition or availability state of a bridge (e.g., open, closed, restricted).
-
B.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
C.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
D.
hasBridgeAccess
Indicates that an entity is permitted to enter or use a specific bridge or bridge-controlled area.
-
E.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6861f3dcc8190992842a0d87b041d |
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.