Triple
T7967999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIEF |
E185252
|
entity |
| Predicate | buyerType |
P809
|
FINISHED |
| Object | importers |
—
|
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: importers | Statement: [CIEF, buyerType, importers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buyerType Context triple: [CIEF, buyerType, importers]
-
A.
buyer
Indicates a relationship where one entity purchases or acquires goods, services, or rights from another entity in exchange for payment or compensation.
-
B.
targetBorrowers
Indicates that certain entities are the intended or eligible recipients of a loan or borrowing arrangement from another entity.
-
C.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
D.
seller
Indicates a relationship where one entity offers or provides goods, services, or assets to another in exchange for payment or other compensation.
-
E.
borrower
Indicates a relationship where one entity temporarily receives and uses something belonging to another entity, typically with the obligation to return it.
- 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd06ee081908c5080003fb7b8f7 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:13 p.m.