Triple
T6252088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clock Tower at the Royal Hospital Chelsea |
E140068
|
entity |
| Predicate | hasDial |
P69726
|
FINISHED |
| Object | clock faces |
—
|
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: clock faces | Statement: [Clock Tower at the Royal Hospital Chelsea, hasDial, clock faces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDial Context triple: [Clock Tower at the Royal Hospital Chelsea, hasDial, clock faces]
-
A.
hasSundial
Indicates that one entity possesses, features, or includes a sundial as part of its attributes or components.
-
B.
dialShape
Indicates the geometric form or outline that characterizes a dial.
-
C.
clockDiameter
Indicates that one entity specifies or measures the diameter of a clock associated with another entity.
-
D.
dialOrientation
Indicates the rotational position or facing direction of a dial relative to a reference point or axis.
-
E.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0633fb2ac8190b71b8e35fa923300 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c05707d5408190a1d0fd80414ad957 |
completed | March 22, 2026, 8:54 p.m. |
Created at: March 22, 2026, 4:24 p.m.