Triple
T34258687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九十九里浜 |
E878965
|
entity |
| Predicate | 歴史的利用 |
P2417
|
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.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
B.
hasHistoriographicalUse
Indicates that something is used or cited within historical writing or analysis as part of constructing, interpreting, or debating historical narratives.
-
C.
historicallyUsedFor
chosen
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
D.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
E.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.