Triple
T37461233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukla, Tyrant of the Vale |
E930920
|
entity |
| Predicate | tokenGenerated |
P189760
|
FINISHED |
| Object | Bananas |
—
|
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: Bananas | Statement: [Mukla, Tyrant of the Vale, tokenGenerated, Bananas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tokenGenerated Context triple: [Mukla, Tyrant of the Vale, tokenGenerated, Bananas]
-
A.
securityGeneration
Indicates the creation or issuance of a security (such as a financial instrument or credential) as a result of some process or action.
-
B.
tokenType
Indicates the classification or category assigned to a token within a sequence, such as its syntactic, semantic, or functional role.
-
C.
tokenClaim
Indicates that an entity asserts ownership of, or entitlement to, a specific token or set of tokens.
-
D.
tokenStatus
Indicates the current state or condition of a token within a process, system, or lifecycle.
-
E.
nativeToken
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.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbca6c066c8190a1599202f341417f |
completed | May 6, 2026, 11:10 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fbc9d0854c8190aa00093274afebb8 |
completed | May 6, 2026, 11:08 p.m. |
Created at: May 3, 2026, 4:17 p.m.