Triple
T8659070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xiamen–Shenzhen Railway |
E205499
|
entity |
| Predicate | railwayLineStatus |
P41715
|
FINISHED |
| Object | in operation |
—
|
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: in operation | Statement: [Xiamen–Shenzhen Railway, railwayLineStatus, in operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayLineStatus Context triple: [Xiamen–Shenzhen Railway, railwayLineStatus, in operation]
-
A.
railStatus
chosen
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
B.
railwayLineNow
Indicates that a previously existing railway line has been replaced, succeeded, or is currently represented by a new or different railway line.
-
C.
railLineStatusAfterward
Indicates the condition or operational status of a rail line after a specified event or time period has occurred.
-
D.
railwayLineUsage
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
E.
railwayTraffic
Indicates the presence, flow, or management of train movements along railway lines between locations.
- 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc486ece68819089c74bdf98b64490 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.