Triple
T26176697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AF |
E654561
|
entity |
| Predicate | canBeExchangedWith |
P27066
|
FINISHED |
| Object | AF' |
—
|
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: AF' | Statement: [AF, canBeExchangedWith, AF']
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeExchangedWith Context triple: [AF, canBeExchangedWith, AF']
-
A.
isExchangedVia
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
B.
exchangedFor
chosen
Indicates that one entity has been traded or substituted in return for another entity.
-
C.
exchangeableAtCentralBank
Indicates that something can be traded in or redeemed at a central bank, typically for another form of value such as legal tender.
-
D.
currencyInterchangeabilityAgreementSince
Indicates that two or more currencies have been mutually accepted as interchangeable under a formal agreement starting from a specified point in time.
-
E.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 26, 2026, 8:38 p.m.