Triple
T33251582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilsandong-gu |
E851256
|
entity |
| Predicate | hasPlannedNewTownArea |
P17383
|
FINISHED |
| Object | Ilsan New Town |
—
|
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: Ilsan New Town | Statement: [Ilsandong-gu, hasPlannedNewTownArea, Ilsan New Town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedNewTownArea Context triple: [Ilsandong-gu, hasPlannedNewTownArea, Ilsan New Town]
-
A.
hasPlannedDistrict
Indicates that an entity is associated with or contains a district that has been formally planned or designated according to an organized development scheme.
-
B.
isPlannedTown
Indicates that a town has been deliberately designed and constructed according to a pre-established plan rather than developing organically over time.
-
C.
hasNewTown
chosen
Indicates that an entity is associated with, or has established, a newly created town.
-
D.
hasPlannedCity
Indicates that an entity has a city that was deliberately designed and constructed according to a prearranged plan.
-
E.
townPlannedWith
Indicates that a town was designed, organized, or laid out in coordination with a particular plan, entity, or planning effort.
- 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_69f34963135c819084e7f1d483421f00 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:31 a.m.