Triple
T3074645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smeaton's Tower |
E64106
|
entity |
| Predicate | relocationEndDate |
P1741
|
FINISHED |
| Object | 1882 |
—
|
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: 1882 | Statement: [Smeaton's Tower, relocationEndDate, 1882]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relocationEndDate Context triple: [Smeaton's Tower, relocationEndDate, 1882]
-
A.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
B.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
C.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
D.
commutationDate
Indicates the date on which a sentence or penalty is formally reduced, altered, or commuted.
-
E.
relocationYear
chosen
Indicates the year in which an entity was moved or transferred from one location to another.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14f5ee0819097ae04b3163dd954 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.