Triple
T8983714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dom Hofmann |
E214598
|
entity |
| Predicate | LootType |
P86164
|
FINISHED |
| Object | NFT project |
—
|
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: NFT project | Statement: [Dom Hofmann, LootType, NFT project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LootType Context triple: [Dom Hofmann, LootType, NFT project]
-
A.
tressureType
Indicates the specific kind or category of tressure (a heraldic ornamental border around a shield or charge) associated with an entity.
-
B.
lootedBy
Indicates that something has been forcibly taken or plundered by a specified agent or group.
-
C.
assetType
Indicates the specific category or classification of an asset within a broader asset framework or system.
-
D.
commodityType
Indicates the classification of a good or product according to its type or category within a commodity system.
-
E.
hasRelicType
Indicates that an entity is associated with, classified by, or possesses a specific type or category of relic.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67eb3cfc8190900a8253cc44621c |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:03 p.m.