Triple
T34953030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jungmi Treaty |
E1008052
|
entity |
| Predicate | legalStatusInKorea |
P200248
|
FINISHED |
| Object | considered invalid and coerced |
—
|
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: considered invalid and coerced | Statement: [Jungmi Treaty, legalStatusInKorea, considered invalid and coerced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusInKorea Context triple: [Jungmi Treaty, legalStatusInKorea, considered invalid and coerced]
-
A.
legalStatusInTaiwan
Indicates the legal status or recognition that an entity has within the jurisdiction of Taiwan.
-
B.
legalStatusInChina
Indicates the legal status or standing that an entity holds under the laws and regulations of China.
-
C.
legalStatusAccordingToIndia
Indicates the legal status or classification of an entity as defined specifically by the laws and regulations of India.
-
D.
legalStatusInNepal
Indicates the legal status or standing that an entity holds under the laws and regulations of Nepal.
-
E.
legalStatusOfPhilippines
Indicates the legal or political status that the Philippines holds in relation to another governing authority or international framework.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff7c96e6dc8190b89554480ebcea39 |
completed | May 9, 2026, 6:27 p.m. |
| PD | Predicate disambiguation | batch_69ff7c2381748190ad9a2176e0e478cd |
completed | May 9, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69ff7c96036c8190bfae5ec9b5a1965f |
completed | May 9, 2026, 6:27 p.m. |
Created at: May 3, 2026, 4 p.m.