Triple
T32889381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JECO |
E841289
|
entity |
| Predicate | isForeignInvestorIn |
P163895
|
FINISHED |
| Object | Chile |
—
|
NE NERFINISHED |
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: Chile | Statement: [JECO, isForeignInvestorIn, Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isForeignInvestorIn Context triple: [JECO, isForeignInvestorIn, Chile]
-
A.
canHoldForeignInvestments
Indicates that an entity is permitted or able to own or maintain investments in foreign countries or foreign-based assets.
-
B.
isForeignIssuerADR
Indicates that an issuer is a foreign company whose shares are represented in the form of American Depositary Receipts (ADRs).
-
C.
investorJurisdiction
chosen
Indicates the legal or regulatory jurisdiction under whose authority the investor is governed or registered.
-
D.
hasPrimaryInvestor
Indicates that an entity has a main or leading investor that provides the primary financial backing or funding.
-
E.
wasForeignIssuerOnNYSE
Indicates that an entity, as a foreign (non-domestic) company, was listed and issued its securities on the New York Stock Exchange during a specified time or context.
- 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_69f349446e288190a70c05bcc4d81172 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.