Triple
T36993910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nihon Kōki |
E915178
|
entity |
| Predicate | coversEventsAfter |
P193754
|
FINISHED |
| Object | Shoku Nihongi |
—
|
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: Shoku Nihongi | Statement: [Nihon Kōki, coversEventsAfter, Shoku Nihongi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversEventsAfter Context triple: [Nihon Kōki, coversEventsAfter, Shoku Nihongi]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
changesAfterEvents
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
-
C.
includesEvents
Indicates that one entity contains or encompasses one or more events as part of its scope or composition.
-
D.
maintainedAfterEvent
Indicates that a state, condition, or relationship continues to hold true after a specified event has occurred.
-
E.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
- F. None of above. chosen
Provenance (4 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
| PDg | Predicate description generation | batch_69fd509cdc5c8190a5f2c451bc0d0b25 |
completed | May 8, 2026, 2:55 a.m. |
Created at: May 3, 2026, 4:14 p.m.