Triple
T4569333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siccar Point unconformity |
E122990
|
entity |
| Predicate | dateOfFamousVisit |
P925
|
FINISHED |
| Object | 1788 |
—
|
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: 1788 | Statement: [Siccar Point unconformity, dateOfFamousVisit, 1788]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFamousVisit Context triple: [Siccar Point unconformity, dateOfFamousVisit, 1788]
-
A.
notableVisit
Indicates that one entity made a visit to another entity or location that is considered significant or noteworthy.
-
B.
inscriptionFamousFor
Indicates that an inscription is widely recognized or notable specifically because of the referenced feature, event, content, or characteristic.
-
C.
papalVisitYear
Indicates the year in which a papal visit (a visit by the Pope) took place.
-
D.
dateOfMainRoyalMonument
Indicates the date on which a person's principal royal monument (such as a main tomb or commemorative structure) was established, completed, or formally dedicated.
-
E.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58a0dfbc81909b5023f0c29addaf |
completed | March 20, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.