Triple
T8635873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Clock Tower |
E204520
|
entity |
| Predicate | clockInstallationDate |
P25196
|
FINISHED |
| Object | 1881 |
—
|
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: 1881 | Statement: [Sapporo Clock Tower, clockInstallationDate, 1881]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockInstallationDate Context triple: [Sapporo Clock Tower, clockInstallationDate, 1881]
-
A.
dateInstalled
Indicates the specific date on which an item, system, or component was installed or put into service.
-
B.
clockShows
Indicates that a clock displays or presents a particular time or temporal value.
-
C.
yearOfOriginalInstallation
chosen
Indicates the specific calendar year when something was first installed or put into initial operation.
-
D.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
E.
clockInput
Indicates that one entity serves as a timing or clock signal input that controls or synchronizes the operation of 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.