Triple
T37150081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AVAX |
E920338
|
entity |
| Predicate | roleOnXChain |
P192102
|
FINISHED |
| Object | medium of exchange |
—
|
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: medium of exchange | Statement: [AVAX, roleOnXChain, medium of exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnXChain Context triple: [AVAX, roleOnXChain, medium of exchange]
-
A.
roleOnCChain
Indicates the specific function or position an entity holds within a particular chain or hierarchical sequence of components or events.
-
B.
roleOn
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
C.
roleOnPern
Indicates the specific function, position, or duty an entity holds within the context of Pern.
-
D.
roleOnAtlasV
Indicates that an entity holds a specific role or function in relation to the Atlas V launch vehicle or program.
-
E.
roleOnVoyager
Indicates the specific position, duty, or function an entity holds in relation to the Voyager mission or project.
- 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_69f76e9f87c08190b4c8f7fafbd8345a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 3, 2026, 4:15 p.m.