Triple
T2079940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Korean won |
E45214
|
entity |
| Predicate | circulationOutsideCountry |
P35647
|
FINISHED |
| Object | very limited |
—
|
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: very limited | Statement: [North Korean won, circulationOutsideCountry, very limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulationOutsideCountry Context triple: [North Korean won, circulationOutsideCountry, very limited]
-
A.
passesThroughCountry
Indicates that a route, path, or object traverses or crosses within the boundaries of a specified country.
-
B.
flowsIntoCountryFrom
Indicates that something (typically a river, resource, or flow) enters and moves into a specified country originating from another location or source.
-
C.
alsoInCountry
Indicates that something located in one country is additionally located or present in another specified country.
-
D.
hasOverseasPresenceIn
Indicates that an entity maintains operations, offices, or activities in a foreign country or region.
-
E.
locatedOutsideJurisdiction
Indicates that one entity is situated beyond the legal or administrative authority area of another entity or governing body.
- F. None of above. chosen
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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.