Triple
T17051549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALGO |
E413707
|
entity |
| Predicate | isSecuredBy |
P1328
|
FINISHED |
| Object | staked ALGO holders |
—
|
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: staked ALGO holders | Statement: [ALGO, isSecuredBy, staked ALGO holders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSecuredBy Context triple: [ALGO, isSecuredBy, staked ALGO holders]
-
A.
securedAgainst
Indicates that one entity is protected or safeguarded against threats, risks, or harmful actions originating from another entity or source.
-
B.
isProtectedBy
chosen
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
D.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
-
E.
securityGuarantee
Indicates a commitment by one party to protect or defend another party against specified threats or risks.
- 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa26e84819098b41ae15618e813 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.