Triple
T32987890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Applied Materials, Inc. |
E843996
|
entity |
| Predicate | hasTradingCountry |
P846
|
FINISHED |
| Object | United States |
E14
|
NE 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: United States | Statement: [Applied Materials, Inc., hasTradingCountry, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTradingCountry Context triple: [Applied Materials, Inc., hasTradingCountry, United States]
-
A.
hasTrade
Indicates a relationship where one entity engages in or maintains a commercial exchange or trading activity with another entity.
-
B.
mainTradingPartnerCountry
Indicates the country that serves as the primary trading partner for a given entity, based on the largest or most significant volume of trade.
-
C.
tradeDestination
Indicates the location or entity to which goods, services, or financial assets are sent or directed as part of a trade transaction.
-
D.
hasCrossBorderTrade
Indicates that there is trade or commercial exchange occurring between entities located in different countries or jurisdictions.
-
E.
hasCountry
chosen
Indicates that one entity possesses, is associated with, or is located within a specific country.
- F. None of above.
Provenance (4 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_69f3494c6f9c8190a255409fce8b1d3b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34e4f8cd20819092caa8b7524a3a44 |
completed | June 19, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 1:22 a.m.