Triple
T19421113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eise Eisinga Planetarium |
E485854
|
entity |
| Predicate | mechanicalDrive |
P135813
|
FINISHED |
| Object | pendulum clockwork |
—
|
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: pendulum clockwork | Statement: [Eise Eisinga Planetarium, mechanicalDrive, pendulum clockwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalDrive Context triple: [Eise Eisinga Planetarium, mechanicalDrive, pendulum clockwork]
-
A.
storageDevice
Indicates a relationship where one entity functions as a device used to store data or digital information for another entity.
-
B.
opticalDrive
Indicates that one entity functions as an optical drive (e.g., CD/DVD/Blu-ray reader/writer) for another entity.
-
C.
hardDriveInterface
Indicates the type of connection standard or protocol through which a hard drive communicates with a computer or controller.
-
D.
hasInternalHardDrive
Indicates that one entity possesses an internal hard drive as a built-in storage component.
-
E.
standardHardDiskCapacity
Indicates the typical or nominal storage capacity of a hard disk as defined by a given standard or specification.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.