Triple
T3524535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ether |
E74505
|
entity |
| Predicate | previouslySecuredBy |
P45445
|
FINISHED |
| Object | proof-of-work |
—
|
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: proof-of-work | Statement: [Ether, previouslySecuredBy, proof-of-work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previouslySecuredBy Context triple: [Ether, previouslySecuredBy, proof-of-work]
-
A.
previouslyLicensedAs
Indicates that an entity held a license under a different name or status at some earlier time.
-
B.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
reauthorizedBy
Indicates that an existing authorization, approval, or mandate has been renewed or extended by a specific agent or authority.
-
D.
previousProtectionStatus
chosen
Indicates the protection or security state an entity was in before its current protection status.
-
E.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
- 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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbc68b15881909b407486946ec3c5 |
completed | March 8, 2026, 6:14 p.m. |
| PD | Predicate disambiguation | batch_69adae121a048190b03825a001d21f49 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:19 p.m.