Triple
T1937674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REN |
E41479
|
entity |
| Predicate | tokenStandard |
P751
|
FINISHED |
| Object | ERC-20 |
—
|
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: ERC-20 | Statement: [REN, tokenStandard, ERC-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tokenStandard Context triple: [REN, tokenStandard, ERC-20]
-
A.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
standardType
chosen
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
C.
hasStandardBearer
Indicates that one entity serves as the official flag- or standard-carrier for another entity, typically in a ceremonial, military, or representative capacity.
-
D.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
E.
standardizedBy
Indicates that one entity defines, regulates, or formalizes the standards or specifications by which another entity is created, measured, or operated.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb2c752fc81909baf38ff1cdeb18c |
completed | March 7, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.