Triple
T5855350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wuhan Metro Line 1 |
E130136
|
entity |
| Predicate | railType |
P14639
|
FINISHED |
| Object | heavy metro |
—
|
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: heavy metro | Statement: [Wuhan Metro Line 1, railType, heavy metro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railType Context triple: [Wuhan Metro Line 1, railType, heavy metro]
-
A.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
B.
railServiceType
Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
-
C.
railwayLineType
chosen
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
D.
thirdRailType
Indicates the specific design or configuration type of a third rail used in an electrified railway system.
-
E.
trainTypeUsed
Indicates that a specific type or category of train is employed or operated in a given context or service.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.