Triple
T28813500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 濃尾平野 |
E727577
|
entity |
| Predicate | 関連工業地帯 |
P49790
|
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.
partOfIndustrialRegion
chosen
Indicates that an entity is located within or belongs to a broader industrial region or industrially developed area.
-
B.
hasIndustrialZoneAlong
Indicates that an industrial zone is located adjacent to or extending along the length of a specified linear feature (such as a road, river, or boundary).
-
C.
containsIndustrialAreas
Indicates that one entity includes or encompasses industrial areas within its boundaries or scope.
-
D.
isIndustrialAreaOf
Indicates that a location functions primarily as an industrial zone or district associated with a specified area or jurisdiction.
-
E.
isIndustrialRegion
Indicates that a given area functions primarily as a center of industrial activity, characterized by significant manufacturing, production, or related industrial operations.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.