Triple
T34098736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Agenda |
E874505
|
entity |
| Predicate | currencyTerm |
P199237
|
FINISHED |
| Object | No Agenda Karma |
—
|
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: No Agenda Karma | Statement: [No Agenda, currencyTerm, No Agenda Karma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyTerm Context triple: [No Agenda, currencyTerm, No Agenda Karma]
-
A.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
currencyPractice
Indicates the customary or standard way a particular currency is used, represented, or managed in transactions or economic contexts.
-
D.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
E.
currencyContext
Indicates that a particular monetary value or transaction is expressed, interpreted, or valid within a specified currency framework or setting.
- 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_69f349a735208190a1dbfb1c2a121059 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff27b125948190aced0fe0189fd39a |
completed | May 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69ff26c30a0481909ef6a54ded851e42 |
completed | May 9, 2026, 12:21 p.m. |
| PDg | Predicate description generation | batch_69ff27b0385c8190bccf340d26268f77 |
completed | May 9, 2026, 12:25 p.m. |
Created at: May 1, 2026, 1:53 a.m.