Triple
T21949865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jam Gadang |
E542035
|
entity |
| Predicate | clockMechanismType |
P130392
|
FINISHED |
| Object | mechanical clock |
—
|
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: mechanical clock | Statement: [Jam Gadang, clockMechanismType, mechanical clock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockMechanismType Context triple: [Jam Gadang, clockMechanismType, mechanical clock]
-
A.
clockMechanism
chosen
Indicates that one entity functions as the internal mechanism or movement that drives the operation of a clock.
-
B.
clockMechanismDesigner
Indicates that one entity is the designer or creator of the mechanism of a clock associated with another entity.
-
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.
clockMechanismCompletedInYear
Indicates that the construction or completion of a clock mechanism occurred in a specified year.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243aed048190b4342899c83b38ec |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:58 p.m.