Triple
T23472025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokcho |
E570153
|
entity |
| Predicate | nationalParkAccess |
P152404
|
FINISHED |
| Object | Seoraksan National Park main entrances |
—
|
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: Seoraksan National Park main entrances | Statement: [Sokcho, nationalParkAccess, Seoraksan National Park main entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalParkAccess Context triple: [Sokcho, nationalParkAccess, Seoraksan National Park main entrances]
-
A.
nationalPark
Indicates that a location is designated and managed as a national park by a governing authority.
-
B.
servesNationalPark
Indicates that an entity provides services or functions in support of a national park.
-
C.
stateParkSystem
Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
-
D.
servedNationalPark
Indicates that an entity has provided official service or worked in an official capacity for a national park.
-
E.
nationalParkName
Indicates the name assigned to a national park.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a700bd0481908047aa4678217cbd |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f07cbbd7488190ab3c8ae7d0fb68bf |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 17, 2026, 5:55 p.m.