Triple
T31905098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Lotman |
E814525
|
entity |
| Predicate | blockReach |
P173468
|
FINISHED |
| Object | about 330 cm |
—
|
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: about 330 cm | Statement: [Paul Lotman, blockReach, about 330 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockReach Context triple: [Paul Lotman, blockReach, about 330 cm]
-
A.
blockExplorer
Indicates that an entity serves as a blockchain explorer interface that allows users to view and inspect transactions, blocks, and related on-chain data for another entity (typically a blockchain network or address).
-
B.
block
Indicates preventing or obstructing another entity’s action, movement, or access.
-
C.
blockchain
Indicates that an entity is associated with, utilizes, or pertains to blockchain technology or distributed ledger systems.
-
D.
blocksLeader
Indicates that one entity prevents or obstructs another entity that is in a leadership role from acting or progressing.
-
E.
chain
Indicates that one entity is linked or connected in sequence to another, typically as part of a series or chain of related elements or actions.
- F. None of above. chosen
Provenance (4 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, midnight