Triple
T5839707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MNT |
E129559
|
entity |
| Predicate | denominationForm |
P5805
|
FINISHED |
| Object | banknotes |
—
|
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: banknotes | Statement: [MNT, denominationForm, banknotes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denominationForm Context triple: [MNT, denominationForm, banknotes]
-
A.
denomination
Indicates the specific religious or organizational branch, sect, or subgroup with which an entity is affiliated.
-
B.
denominationType
chosen
Indicates the specific category or kind of denomination associated with an entity, such as its type within a broader classification of denominations.
-
C.
denominationName
Indicates the specific religious or organizational denomination to which an entity belongs or is associated.
-
D.
denominationSystem
Indicates a relationship where one entity defines, uses, or belongs to a particular system of denominations (such as units, values, or classifications) established by another entity.
-
E.
denominationContext
Indicates the contextual or situational framework within which a particular denomination, classification, or named unit is defined or interpreted.
- 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_69c0084af79c81908af128ccc29983d0 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:54 p.m.