Triple
T30260799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 남구 |
E769484
|
entity |
| Predicate | isPartOfNamingSystem |
P1285
|
FINISHED |
| Object | 방위 기반 구 명칭 체계 |
—
|
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: 방위 기반 구 명칭 체계 | Statement: [남구, isPartOfNamingSystem, 방위 기반 구 명칭 체계]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfNamingSystem Context triple: [남구, isPartOfNamingSystem, 방위 기반 구 명칭 체계]
-
A.
usesNamingSystem
Indicates that one entity adopts or applies a particular naming system or convention to identify or label other entities.
-
B.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
-
C.
isPartOfRepresentationSystem
Indicates that one entity functions as a component or element within a broader representational system (such as a notation, coding scheme, or symbolic framework).
-
D.
isPartOfStandardizationSystem
Indicates that something belongs to, or is included within, a defined standardization framework, scheme, or system.
-
E.
namingBasis
Indicates that one entity serves as the reason, source, or criterion for how another entity is named or designated.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
Created at: April 29, 2026, 7:42 p.m.