Triple
T38665077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京浜急行電鉄株式会社 |
E940432
|
entity |
| Predicate | 路線ブランド |
P64700
|
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.
brandLine
chosen
Indicates that one brand is a specific product line or sub-brand offered under another brand.
-
B.
lineName
Indicates the specific name or designation assigned to a particular line (such as a route, path, or service) that distinguishes it from other lines.
-
C.
brandNumber
Indicates the identifying number or code assigned to a particular brand within a system or dataset.
-
D.
commuterBrand
Indicates a relationship where a brand is specifically associated with or targeted toward commuter use or commuting contexts.
-
E.
notableTrainBrand
Indicates that an entity is a well-known or significant brand associated with trains or railway services.
- 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_69f76edfde348190bf6529d9f49ecd62 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.