Triple
T17051522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALGO |
E413707
|
entity |
| Predicate | underlyingTechnology |
P38305
|
FINISHED |
| Object | blockchain |
—
|
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: blockchain | Statement: [ALGO, underlyingTechnology, blockchain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingTechnology Context triple: [ALGO, underlyingTechnology, blockchain]
-
A.
technologyBasis
chosen
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
-
B.
underlyingCompanyKeyTechnology
Indicates that a specific technology serves as a core or foundational technological component for a given company.
-
C.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
D.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
E.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another 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_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.