Triple
T28813425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 富士川 |
E727575
|
entity |
| Predicate | 歴史的事件 |
P2107
|
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.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicalEventsDescribed
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
C.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
-
D.
歴史
Indicates a relationship where something pertains to, records, or is involved in the events, development, or study of the past over time.
-
E.
historicalIssue
Indicates that one entity is a past or previously existing edition, version, or instance of another entity, typically within a chronological sequence.
- 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.