Triple
T18213463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zytglogge |
E436090
|
entity |
| Predicate | hasClockMechanismDate |
P130264
|
FINISHED |
| Object | early 16th 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: early 16th century | Statement: [Zytglogge, hasClockMechanismDate, early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockMechanismDate Context triple: [Zytglogge, hasClockMechanismDate, early 16th century]
-
A.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
hasClockFigures
Indicates that an object features or includes figures or representations that are part of a clock.
-
C.
hasClockMaker
Indicates that an entity has, is associated with, or was created/maintained by a specific clock maker.
-
D.
chronometerNumber
Indicates that an entity has been assigned a specific chronometer identification number, linking it to that unique timekeeping device record.
-
E.
hasClockFaces
Indicates that an object is equipped with one or more clock faces.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e475953c81909f792793ded2057e |
completed | April 19, 2026, 2:19 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
| PDg | Predicate description generation | batch_69e438f684e48190b38c64b58c518b6a |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 10:32 a.m.