Triple
T26434560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Caithness |
E664603
|
entity |
| Predicate | originalCreationDate |
P7360
|
FINISHED |
| Object | circa 1455 |
—
|
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: circa 1455 | Statement: [Earl of Caithness, originalCreationDate, circa 1455]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCreationDate Context triple: [Earl of Caithness, originalCreationDate, circa 1455]
-
A.
effectiveCreationDate
Indicates the date on which something actually comes into effect or becomes valid, as opposed to when it was merely created or recorded.
-
B.
createdAt
chosen
Indicates the date and time at which an entity was initially created or came into existence.
-
C.
laterCreationDate
Indicates that one entity was created at a later date or time than the other entity.
-
D.
firstCreationEndDate
Indicates the date on which the initial creation or establishment of something was completed or came to an end.
-
E.
createdAtEvent
Indicates the specific event during which the entity was originally created.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 26, 2026, 11:52 p.m.