Triple
T10698250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bracken House |
E252200
|
entity |
| Predicate | hasClockFeature |
P5737
|
FINISHED |
| Object | zodiac clock with portrait of Winston Churchill |
—
|
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: zodiac clock with portrait of Winston Churchill | Statement: [Bracken House, hasClockFeature, zodiac clock with portrait of Winston Churchill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockFeature Context triple: [Bracken House, hasClockFeature, zodiac clock with portrait of Winston Churchill]
-
A.
hasClock
chosen
Indicates that one entity possesses, contains, or is equipped with a clock.
-
B.
hasClockInput
Indicates that an entity receives a clock signal from another entity as an input for timing or synchronization purposes.
-
C.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
D.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
E.
hasClockSpeed
Indicates that an entity (typically a processor or device) operates at a specified clock frequency or speed.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd8a03848190bf68dd470bee103a |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.