Triple
T30407108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogecoin |
E773508
|
entity |
| Predicate | usesAddressPrefix |
P93740
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [Dogecoin, usesAddressPrefix, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddressPrefix Context triple: [Dogecoin, usesAddressPrefix, D]
-
A.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
B.
addressExamplePrefix
Indicates that an address example is introduced or categorized by a specific prefix string used to distinguish or group it.
-
C.
usedAsPrefixIn
chosen
Indicates that one element functions as a leading prefix component in the formation or representation of another element.
-
D.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
E.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 8:04 p.m.