Triple
T15392414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 長堀鶴見緑地線 |
E368079
|
entity |
| Predicate | 所在国の鉄道事業者種別 |
P38622
|
FINISHED |
| Object | 公営から民営化された地下鉄事業者 |
—
|
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: 公営から民営化された地下鉄事業者 | Statement: [長堀鶴見緑地線, 所在国の鉄道事業者種別, 公営から民営化された地下鉄事業者]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在国の鉄道事業者種別 Context triple: [長堀鶴見緑地線, 所在国の鉄道事業者種別, 公営から民営化された地下鉄事業者]
-
A.
railwayCompanyType
chosen
Indicates the specific category or classification of a railway company in terms of its role, ownership, or operational type.
-
B.
isNationalRailwaySystemOf
Indicates that one entity functions as the official national railway system serving and operating within the territory of another entity.
-
C.
railwayCompany
Indicates that one entity is a railway company that owns, operates, or manages railway services or infrastructure in relation to another entity.
-
D.
formerRailOperator
Indicates that an entity previously operated a rail service or railway system but no longer does so.
-
E.
railwayOwner
Indicates that one entity owns, controls, or holds proprietary rights over a railway or railway system used by another entity.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7838b48190862b43c6c8620692 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.