Triple
T6783512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TO |
E155741
|
entity |
| Predicate | associatedWithCurrencyCode |
P12372
|
FINISHED |
| Object | TOP |
—
|
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: TOP | Statement: [TO, associatedWithCurrencyCode, TOP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCurrencyCode Context triple: [TO, associatedWithCurrencyCode, TOP]
-
A.
associatedCurrencyCode
chosen
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
B.
hasAssociatedCurrencyEntity
Indicates that an entity is linked to a specific currency entity that represents the monetary unit relevant to it.
-
C.
associatedWithExchange
Indicates a relationship in which an entity is linked or connected to a particular exchange or trading platform.
-
D.
linkedByCurrencyArrangementWith
Indicates that two entities are connected through a formal currency-related arrangement, such as a peg, union, swap line, or other structured monetary linkage.
-
E.
involvesCurrency
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28bdc3c8190aa60616d89db66ed |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.