Triple
T34119565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keisei Main Line |
E875077
|
entity |
| Predicate | isPrivateRailway |
P138892
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Keisei Main Line, isPrivateRailway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPrivateRailway Context triple: [Keisei Main Line, isPrivateRailway, true]
-
A.
hasPrivateRailway
chosen
Indicates that an entity owns or operates a railway line that is privately controlled rather than part of a public or national rail system.
-
B.
isPublicRailway
Indicates that a railway is designated for public use and accessible to the general population rather than being privately restricted.
-
C.
isTouristRailway
Indicates that a railway is primarily operated for tourism or leisure purposes rather than as a regular public transport service.
-
D.
isRailwayIn
Indicates that a railway is located within or passes through a specified geographic or administrative area.
-
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_69f349a9271c81909576994c9ef7b179 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:53 a.m.