Triple
T843395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanyang |
E18224
|
entity |
| Predicate | railAndRiverJunction |
P14465
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hanyang, railAndRiverJunction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railAndRiverJunction Context triple: [Hanyang, railAndRiverJunction, yes]
-
A.
railwayJunctionFor
Indicates that a location serves as a junction point where multiple railway lines or routes connect or intersect for a given railway network or service.
-
B.
railTracks
Indicates that one entity consists of, includes, or is associated with rail tracks used for guiding trains or rail vehicles.
-
C.
junctionStation
chosen
Indicates that a station functions as a junction where multiple routes or lines intersect or connect.
-
D.
railroad
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
E.
railwayLine
Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
- 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_69a4938b04208190b82e1df6b572c548 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7f396c8190aa8b8dfbe0b4f732 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.