Triple
T24367505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GATS Annexes |
E614236
|
entity |
| Predicate | modeOfSupplyCovered |
P152430
|
FINISHED |
| Object | cross-border supply |
—
|
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: cross-border supply | Statement: [GATS Annexes, modeOfSupplyCovered, cross-border supply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfSupplyCovered Context triple: [GATS Annexes, modeOfSupplyCovered, cross-border supply]
-
A.
modeOfSupplyConcerned
Indicates the specific method or channel through which a product, service, or resource is provided or delivered is the focus of consideration.
-
B.
typeOfTaxpayerCovered
Indicates the category or kind of taxpayer to which a particular rule, obligation, or provision applies.
-
C.
supplyMode
chosen
Indicates the manner or method by which something is provided, delivered, or made available.
-
D.
hasCoverageRestriction
Indicates that there is a limitation, exclusion, or condition applied to the scope or extent of coverage provided.
-
E.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
- 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_69e2d7e1e010819098b95eb3f905943d |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29388c9308190a7a70bf75ed1501c |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.