Triple
T30407132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogecoin |
E773508
|
entity |
| Predicate | hasTransactionConfirmationTarget |
P197052
|
FINISHED |
| Object | about 1 minute per block |
—
|
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 1 minute per block | Statement: [Dogecoin, hasTransactionConfirmationTarget, about 1 minute per block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransactionConfirmationTarget Context triple: [Dogecoin, hasTransactionConfirmationTarget, about 1 minute per block]
-
A.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
B.
hasSettlementAround
Indicates that a settlement is located in the surrounding area of a specified place or feature.
-
C.
hasTarget
Indicates that one entity is directed toward, aimed at, or intended to affect another specific entity as its target.
-
D.
covenantConfirmedWith
Indicates that a formal, binding agreement or promise has been ratified or validated between one party and another.
-
E.
hasSettlementOnBanks
Indicates that a settlement is located on or along the banks of a geographic feature such as a river, lake, or coastline.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69fe7663b5bc81909524c40d3a172512 |
completed | May 8, 2026, 11:48 p.m. |
Created at: April 29, 2026, 8:04 p.m.