Triple
T455240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Clearing Union |
E7218
|
entity |
| Predicate | coreFeature |
P7153
|
FINISHED |
| Object | use of a supranational currency unit |
—
|
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: use of a supranational currency unit | Statement: [International Clearing Union, coreFeature, use of a supranational currency unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreFeature Context triple: [International Clearing Union, coreFeature, use of a supranational currency unit]
-
A.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
B.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
E.
featuresText
Indicates that an entity includes or presents a specific piece of text as one of its characteristics or contents.
- 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef87cc7c8190a0fec933457821e2 |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.