Triple
T14007990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annales Cambriae |
E337000
|
entity |
| Predicate | earliestSurvivingVersionDate |
P35832
|
FINISHED |
| Object | mid-10th century |
—
|
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: mid-10th century | Statement: [Annales Cambriae, earliestSurvivingVersionDate, mid-10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestSurvivingVersionDate Context triple: [Annales Cambriae, earliestSurvivingVersionDate, mid-10th century]
-
A.
earliestVersionDate
chosen
Indicates the date on which the earliest known or first version of an entity was created, released, or became valid.
-
B.
earliestStrataDate
Indicates the earliest known or recorded date associated with a particular geological or archaeological stratum.
-
C.
firstVersionYear
Indicates the calendar year in which the first version or initial release of something was created, published, or made available.
-
D.
earliestFabricDate
Indicates the earliest date at which the fabric (or material) associated with an entity was created or first produced.
-
E.
earliestAttestedStatus
Indicates the earliest known or recorded status that has been documented for an entity.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed44f90819099ad08c09c066b56 |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:19 p.m.