Triple
T35504640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 3 (Shijiazhuang Metro) |
E1026107
|
entity |
| Predicate | isRailTransport |
P110338
|
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: [Line 3 (Shijiazhuang Metro), isRailTransport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRailTransport Context triple: [Line 3 (Shijiazhuang Metro), isRailTransport, yes]
-
A.
isPassengerRail
Indicates that something functions as or is classified as a passenger rail service or system, primarily used to transport people rather than freight.
-
B.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
C.
isRailServiceOf
Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
-
D.
isRailInfrastructure
chosen
Indicates that something functions as or is classified as part of a railway-related physical infrastructure or system.
-
E.
isElectricRailway
Indicates that a given railway system operates using electric power rather than diesel or other forms of propulsion.
- 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_69f76dfd61208190b93ec6dc439cab41 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.