Triple
T28482958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nopo |
E720743
|
entity |
| Predicate | hasExpressBusConnectionsTo |
P3791
|
FINISHED |
| Object | other regions of South Korea |
—
|
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: other regions of South Korea | Statement: [Nopo, hasExpressBusConnectionsTo, other regions of South Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressBusConnectionsTo Context triple: [Nopo, hasExpressBusConnectionsTo, other regions of South Korea]
-
A.
providesRailConnectionsWithin
Indicates that an entity offers or facilitates rail transport links connecting locations inside a specified area or region.
-
B.
hasPassengerRailConnection
Indicates that there exists a passenger rail service linking one location or transport node to another.
-
C.
hasFareGateConnectionTo
Indicates that there is a direct passage or connection between two areas that is controlled or mediated by fare gates.
-
D.
hasPublicTransportConnection
chosen
Indicates that there is an available public transportation link or service connecting the related entities.
-
E.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
- 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_69f01a5a47148190b0a7e111bc432e0a |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 2:56 a.m.