Triple
T31046519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zuihoden |
E791140
|
entity |
| Predicate | originallyCompletedIn |
P39330
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Zuihoden, originallyCompletedIn, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyCompletedIn Context triple: [Zuihoden, originallyCompletedIn, 17th century]
-
A.
originalCompletionDate
chosen
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
B.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
C.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
D.
completedFor
Indicates that one entity has finished or fulfilled a task, process, or obligation on behalf of or in service to another entity.
-
E.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a007aa8d3a481908543f9b5d562a90c |
completed | May 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a007a44996481908688ccfdbc56511d |
completed | May 10, 2026, 12:29 p.m. |
Created at: April 29, 2026, 8:59 p.m.