Triple
T27311274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasang-gu |
E689213
|
entity |
| Predicate | hasNotableDong |
P196776
|
FINISHED |
| Object | Gwaebeop-dong |
—
|
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: Gwaebeop-dong | Statement: [Sasang-gu, hasNotableDong, Gwaebeop-dong]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableDong Context triple: [Sasang-gu, hasNotableDong, Gwaebeop-dong]
-
A.
hasNotableFeature
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
B.
hasNotableItem
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
C.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
-
E.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
- 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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
| PDg | Predicate description generation | batch_69fe68a385f48190b942700e3eddc9b6 |
completed | May 8, 2026, 10:50 p.m. |
Created at: April 27, 2026, 11:28 a.m.