Triple
T30460312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geumjeong-gu |
E774985
|
entity |
| Predicate | hasExpressBusTerminal |
P5891
|
FINISHED |
| Object | Busan Central Bus Terminal |
—
|
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: Busan Central Bus Terminal | Statement: [Geumjeong-gu, hasExpressBusTerminal, Busan Central Bus Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpressBusTerminal Context triple: [Geumjeong-gu, hasExpressBusTerminal, Busan Central Bus Terminal]
-
A.
hasBusTerminalType
Indicates the specific category or type of bus terminal associated with an entity.
-
B.
hasPassengerTerminal
Indicates that one entity possesses or is equipped with a passenger terminal used for boarding, alighting, or handling passengers.
-
C.
hasPassengerTerminalFunction
Indicates that something serves the role or performs the function of a passenger terminal, supporting the handling and movement of passengers.
-
D.
hasBusStation
chosen
Indicates that a place or area contains or is served by a bus station.
-
E.
hasBusInterchange
Indicates that one transport-related entity includes, contains, or is associated with a bus interchange facility.
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 29, 2026, 8:10 p.m.