Triple
T27078892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sungkyunkwan University |
E685539
|
entity |
| Predicate | Suwon CampusLocatedIn |
P13918
|
FINISHED |
| Object | Suwon, Gyeonggi-do |
—
|
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: Suwon, Gyeonggi-do | Statement: [Sungkyunkwan University, Suwon CampusLocatedIn, Suwon, Gyeonggi-do]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Suwon CampusLocatedIn Context triple: [Sungkyunkwan University, Suwon CampusLocatedIn, Suwon, Gyeonggi-do]
-
A.
hasCampusOn
Indicates that an institution or organization maintains a campus located on a specified geographic area or site.
-
B.
campus1
Indicates a relationship where an entity is identified as a campus or is located on/associated with a particular campus.
-
C.
universityLocatedIn
chosen
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
D.
campusOfNationalUniversity
Indicates that one entity is a campus belonging to or administered by a national university.
-
E.
cityCampusServes
Indicates that a city campus provides services, resources, or support to a particular population, area, or institution.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231822ac8190887ebcb3b6d86d2b |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:33 a.m.