Triple
T2578105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bancor |
E57023
|
entity |
| Predicate | notAdoptedBecause |
P37898
|
FINISHED |
| Object | preference for US dollar as reserve currency |
—
|
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: preference for US dollar as reserve currency | Statement: [Bancor, notAdoptedBecause, preference for US dollar as reserve currency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notAdoptedBecause Context triple: [Bancor, notAdoptedBecause, preference for US dollar as reserve currency]
-
A.
notRecommendedBy
Indicates that one entity explicitly advises against or does not endorse another entity.
-
B.
rejectedBecause
chosen
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
C.
adopts
Indicates that one entity formally takes another into its care, control, or use, assuming ongoing responsibility or ownership.
-
D.
adopted
Indicates that one entity has legally taken another (often a child or animal) into its family or care as a permanent member.
-
E.
adoptedAs
Indicates that one entity has taken another into its family or care through a formal or recognized adoption process.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a86f9881908df29a7caaf9a7df |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.