Triple
T2434607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianmen |
E52925
|
entity |
| Predicate | railTransport |
P18201
|
FINISHED |
| Object | served by regional rail lines |
—
|
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: served by regional rail lines | Statement: [Tianmen, railTransport, served by regional rail lines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railTransport Context triple: [Tianmen, railTransport, served by regional rail lines]
-
A.
trains
Indicates that one entity teaches, instructs, or coaches another entity to develop skills, knowledge, or abilities.
-
B.
railroad
chosen
Indicates that one entity constructs, operates, or provides railroad or train transportation services for another entity or area.
-
C.
railcode
Indicates that an entity is associated with a specific railway code used for identification or classification within a rail system.
-
D.
railSystemType
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
-
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_69ab4959bcc0819083246f9fb10439e3 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abcebf7cac8190889e6890d72c256c |
completed | March 7, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69abc5ac11b081908ce6a506e81a742a |
completed | March 7, 2026, 6:29 a.m. |
Created at: March 6, 2026, 9:43 p.m.