Triple
T33329548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 仁徳天皇 |
E853363
|
entity |
| Predicate | 記述史料 |
P55104
|
FINISHED |
| Object | 日本書紀 |
—
|
NE NERFINISHED |
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.
historicalMaterial
Indicates that something serves as a source or document providing information or evidence about past events or conditions.
-
B.
historicalRecord
Indicates that there exists a documented account or record capturing information about an entity, event, or relationship from the past.
-
C.
historianDescribing
Indicates that a historian is providing an account, explanation, or interpretation of a subject, event, or entity.
-
D.
historicallyDocumentedBy
chosen
Indicates that information about an entity or event is recorded or attested in a specific historical document or source.
-
E.
historicalWork
Indicates that one entity is a work (such as a document, artifact, or creation) that originates from or pertains to a past historical period in relation to another entity.
- 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_69f34969614c81909cd99661b0902533 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.