Triple
T37061760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 京阪電気鉄道本社 |
E917340
|
entity |
| Predicate | 関連業種 |
P167291
|
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.
hasRelativeInSameIndustry
Indicates that one entity has a relative who works in the same industry as the entity.
-
B.
relationToIndustry
Indicates how an entity is connected or relevant to a particular industry, such as through involvement, impact, or association.
-
C.
containsIndustry
Indicates that one entity includes or encompasses a particular industry within its scope, structure, or operations.
-
D.
concernedIndustry
chosen
Indicates the industry or sector that is affected by, involved in, or relevant to a given entity, action, or issue.
-
E.
supportedIndustry
Indicates that one entity provides backing, resources, or services to help sustain or advance a particular industry.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.