Triple
T30406953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polygon |
E773505
|
entity |
| Predicate | token |
P49249
|
FINISHED |
| Object | MATIC |
—
|
NE NERFINISHED |
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: MATIC | Statement: [Polygon, token, MATIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: token Context triple: [Polygon, token, MATIC]
-
A.
tokenType
Indicates the classification or category assigned to a token within a sequence, such as its syntactic, semantic, or functional role.
-
B.
tokenizerType
Indicates the specific tokenization method or algorithm used to split text into tokens.
-
C.
key
Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
-
D.
nativeToken
chosen
Indicates that the referenced token is the primary, built-in cryptocurrency or asset of a given blockchain or platform, as opposed to a secondary or issued token.
-
E.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
- 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_69f686204b2c8190afea8470275fd875 |
completed | May 2, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:04 p.m.