Triple
T24094340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton Court astronomical clock |
E596872
|
entity |
| Predicate | mechanismBy |
P155054
|
FINISHED |
| Object | Nicholas Oursian |
—
|
NE NERFINISHED |
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: Nicholas Oursian | Statement: [Hampton Court astronomical clock, mechanismBy, Nicholas Oursian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanismBy Context triple: [Hampton Court astronomical clock, mechanismBy, Nicholas Oursian]
-
A.
mechanismExample
Indicates that one entity serves as an illustrative example of the mechanism or process by which another entity operates or produces an effect.
-
B.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
C.
mentionsMechanism
Indicates that one entity explicitly refers to or describes the mechanism, process, or causal pathway by which another entity operates or produces an effect.
-
D.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
E.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
- 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_69e288c548048190a5c1018da1166a21 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dd2332b48190a711b2a0a304f3c2 |
completed | April 29, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f17651458c8190bbfd301883e46085 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f17b58012c81909106b332db399023 |
completed | April 29, 2026, 3:30 a.m. |
Created at: April 17, 2026, 10:58 p.m.