Triple
T10012767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | POSZT |
E199412
|
entity |
| Predicate | internationalDimension |
P1499
|
FINISHED |
| Object | invites foreign companies |
—
|
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: invites foreign companies | Statement: [POSZT, internationalDimension, invites foreign companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: internationalDimension Context triple: [POSZT, internationalDimension, invites foreign companies]
-
A.
isInternational
chosen
Indicates that something has a connection to, involves, or extends across more than one country.
-
B.
intercontinental
Indicates a relationship or action that spans or connects multiple continents.
-
C.
internationalAffairsFunction
Indicates a functional role or responsibility related to managing, coordinating, or influencing interactions and relationships between entities across national borders.
-
D.
internationalConcern
Indicates that an issue, event, or situation is regarded as significant or problematic by multiple countries or the international community as a whole.
-
E.
internationalUsage
Indicates that something is used or applied across multiple countries or in an international 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd3cf5b881908f5318e55bdd22b6 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:52 p.m.