Triple
T2223261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Tower |
E48188
|
entity |
| Predicate | clockMechanismCompletedInYear |
P37139
|
FINISHED |
| Object | 1854 |
—
|
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: 1854 | Statement: [Elizabeth Tower, clockMechanismCompletedInYear, 1854]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clockMechanismCompletedInYear Context triple: [Elizabeth Tower, clockMechanismCompletedInYear, 1854]
-
A.
clockType
Indicates the type or category of a clock associated with an entity (e.g., analog, digital, system clock, etc.).
-
B.
hasClock
Indicates that one entity possesses, contains, or is equipped with a clock.
-
C.
usesClockSystem
Indicates that one entity employs or operates according to the clock or timekeeping system defined or provided by another entity.
-
D.
hasClockTower
Indicates that one entity possesses or features a clock tower as part of its structure or property.
-
E.
timekeepingAccuracy
Indicates how closely an entity’s measurement or tracking of time matches the true or standard reference time.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03d1df88190950c691a4c246bd1 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbfe93d7c81909f1b9c1b1e3c7989 |
completed | March 7, 2026, 6:04 a.m. |
Created at: March 4, 2026, 7:47 p.m.