Triple
T26699992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kim Bang District |
E673126
|
entity |
| Predicate | hasTransportAccessibility |
P149690
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Kim Bang District, hasTransportAccessibility, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportAccessibility Context triple: [Kim Bang District, hasTransportAccessibility, high]
-
A.
hasTransitAccessTo
Indicates that one place or entity is reachable from another via public or shared transportation services.
-
B.
accessibleByPublicTransport
chosen
Indicates that a location or entity can be reached using public transportation services such as buses, trains, or trams.
-
C.
hasPublicTransitFunction
Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
-
D.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
E.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 27, 2026, 3:31 a.m.