Triple
T18373464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES |
E446246
|
entity |
| Predicate | usedAsCountryIdentifierIn |
P41324
|
FINISHED |
| Object | international data exchange |
—
|
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: international data exchange | Statement: [ES, usedAsCountryIdentifierIn, international data exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsCountryIdentifierIn Context triple: [ES, usedAsCountryIdentifierIn, international data exchange]
-
A.
usedForCountry
Indicates that something is used for, or serves a purpose related to, a specific country.
-
B.
identifiesCountryIn
chosen
Indicates that one entity specifies or determines which country another entity is associated with or located in.
-
C.
usedByCountryCode
Indicates that something is utilized or applied within the country identified by the given country code.
-
D.
usedWithCountryName
Indicates that something (such as a term, label, or identifier) is used specifically in conjunction with a country name.
-
E.
usedInCountry
Indicates that something is utilized, applied, or in operation within the specified country.
- 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_69d8b9f370b88190b1e5081c2c238e7f |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e517561edc8190b5d2834707ab662b |
completed | April 19, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:45 a.m.