Triple
T29821373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seomyeon commercial district |
E757252
|
entity |
| Predicate | isMajorDowntownAreaOf |
P164
|
FINISHED |
| Object | Busan |
—
|
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: Busan | Statement: [Seomyeon commercial district, isMajorDowntownAreaOf, Busan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorDowntownAreaOf Context triple: [Seomyeon commercial district, isMajorDowntownAreaOf, Busan]
-
A.
isMajorCityIn
Indicates that a city is a primary or significant urban center located within a specified larger region or country.
-
B.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
-
C.
isMajorCenterOf
chosen
Indicates that a place serves as a primary hub or focal point for a particular activity, function, or domain.
-
D.
hasMajorCity
Indicates that a location possesses at least one city of significant size, importance, or influence within its region or country.
-
E.
cityOfMajorPresence
Indicates that an entity has a significant or primary operational, demographic, or functional presence in the specified city.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 29, 2026, 5:29 p.m.