Triple
T25849946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 六甲山地 |
E651172
|
entity |
| Predicate | 歴史 |
P9609
|
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.
politicalHistory
Indicates that there exists a historical political relationship, involvement, or background connecting the entities, such as past offices held, affiliations, or political events linking them.
-
B.
ethnicHistory
Indicates a relationship where one entity documents, describes, or is associated with the historical development, experiences, or heritage of an ethnic group.
-
C.
historicalCategory
chosen
Indicates that an entity is classified within a particular historical grouping, period, or type based on its time-related characteristics or context.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
countryHistoryTopic
Indicates that a subject is associated with a historical topic, theme, or aspect specifically related to a particular country.
- 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_69e7ab39035c8190be15c8aaee1bb858 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6023ac9e48190b60639f667445ace |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 7:58 a.m.