Triple
T5049126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaesong Industrial Region |
E113740
|
entity |
| Predicate | plannedArea |
P60867
|
FINISHED |
| Object | approximately 66 square kilometers |
—
|
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: approximately 66 square kilometers | Statement: [Kaesong Industrial Region, plannedArea, approximately 66 square kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedArea Context triple: [Kaesong Industrial Region, plannedArea, approximately 66 square kilometers]
-
A.
partOfPlanningRegion
Indicates that one entity is included within, or belongs to, a larger designated planning region.
-
B.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
C.
plannedFacility
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
D.
areaComponent
Indicates that one area is a constituent or sub-area that forms part of a larger area.
-
E.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:37 p.m.