Triple
T23240710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monumental Clock Tower |
E581432
|
entity |
| Predicate | hasClockFacesOrientation |
P53371
|
FINISHED |
| Object | four cardinal directions |
—
|
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: four cardinal directions | Statement: [Monumental Clock Tower, hasClockFacesOrientation, four cardinal directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClockFacesOrientation Context triple: [Monumental Clock Tower, hasClockFacesOrientation, four cardinal directions]
-
A.
hasClockFaces
Indicates that an object is equipped with one or more clock faces.
-
B.
hasClockFigures
Indicates that an object features or includes figures or representations that are part of a clock.
-
C.
bellOrientation
Indicates the spatial direction or alignment in which a bell is positioned or facing.
-
D.
clockShows
Indicates that a clock displays or presents a particular time or temporal value.
-
E.
designedToFace
chosen
Indicates that one entity has been intentionally oriented or configured so that its front, surface, or primary direction points toward another entity or reference direction.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192edd974819093a57456e7b12a03 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.