Triple
T15264219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dencun |
E364857
|
entity |
| Predicate | addsDataType |
P33715
|
FINISHED |
| Object | blob-carrying transactions |
—
|
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: blob-carrying transactions | Statement: [Dencun, addsDataType, blob-carrying transactions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsDataType Context triple: [Dencun, addsDataType, blob-carrying transactions]
-
A.
addsFeatureType
Indicates that one entity introduces or incorporates a specific feature type into another entity or system.
-
B.
dataTypes
chosen
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
C.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
-
D.
registerType
Indicates that an entity is classified or recorded under a specific type or category within a registration system.
-
E.
appliesToDataType
Indicates that a rule, operation, or construct is specifically intended to be used with, or is valid for, a particular data type.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0084fed0481908e452c89cba2be82 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.