Triple
T4660650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zytglogge |
E102519
|
entity |
| Predicate | clockMechanismDate |
P37139
|
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, clockMechanismDate, early 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockMechanismDate Context triple: [Zytglogge, clockMechanismDate, early 16th century]
-
A.
clockMechanismDesigner
Indicates that one entity is the designer or creator of the mechanism of a clock associated with another entity.
-
B.
clockMechanismCompletedInYear
chosen
Indicates that the construction or completion of a clock mechanism occurred in a specified year.
-
C.
clockMechanismEngineer
Indicates that one entity is an engineer who designs, builds, or maintains clock mechanisms for another entity or context.
-
D.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
E.
clockDiameter
Indicates that one entity specifies or measures the diameter of a clock associated with 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd632a17cc8190bcdab0a13b89f5c0 |
completed | March 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69bd62126b0c81909ba3f21b21e30d54 |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:15 p.m.