Triple
T29421373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FI |
E746164
|
entity |
| Predicate | usedInInternationalTradeDocuments |
P511
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [FI, usedInInternationalTradeDocuments, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInInternationalTradeDocuments Context triple: [FI, usedInInternationalTradeDocuments, yes]
-
A.
usedInInternationalTrade
chosen
Indicates that something participates as a good, service, or instrument in commercial exchanges between different countries.
-
B.
usedInInternationalMail
Indicates that something is employed or applicable in the context of international mail services or cross-border postal operations.
-
C.
usedForTradeBetween
Indicates that something serves as a medium, instrument, or basis for trade or exchange between two or more parties.
-
D.
usedInFinancialDocuments
Indicates that something is employed or appears within financial documents or records.
-
E.
usedInConstituentCountry
Indicates that something is utilized or applied within a specific constituent country of a larger sovereign state.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 28, 2026, 3:06 p.m.