Triple
T26096451
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AAD |
E658279
|
entity |
| Predicate | hasMonetaryFunction |
P35955
|
FINISHED |
| Object | unit of account |
—
|
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: unit of account | Statement: [AAD, hasMonetaryFunction, unit of account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonetaryFunction Context triple: [AAD, hasMonetaryFunction, unit of account]
-
A.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
B.
monetaryFunction
chosen
Indicates a relationship where something serves a financial role, such as handling, managing, or affecting money or economic value.
-
C.
isFinancialMechanismFor
Indicates a relationship where one entity serves as the means, instrument, or structure through which another entity is financed, funded, or economically supported.
-
D.
monetaryStatus
Indicates the financial condition or situation of an entity, such as its wealth, solvency, or level of monetary resources.
-
E.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 26, 2026, 7:51 p.m.