Triple
T24756220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengdu South railway station |
E619291
|
entity |
| Predicate | servesRail |
P55099
|
FINISHED |
| Object | regional rail |
—
|
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: regional rail | Statement: [Chengdu South railway station, servesRail, regional rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesRail Context triple: [Chengdu South railway station, servesRail, regional rail]
-
A.
servesRailCorridor
Indicates that something (such as a service, facility, or operation) provides service to or operates along a specific rail corridor.
-
B.
servedByRailroad
Indicates that a location or facility is provided with transportation or service by a railroad line or company.
-
C.
hasRailServiceAt
Indicates that a rail transport service operates at or serves a particular location or facility.
-
D.
servedByRailBranch
Indicates that a location or facility is connected to and provided service by a specific railway branch line.
-
E.
railwayTypeServed
chosen
Indicates the type of railway system or service that a given entity (such as a station, line, or facility) is designed to serve or accommodate.
- 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_69e2fabb349881908a13a212a0221a63 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 4:26 a.m.