Triple
T24977263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham cave system |
E625056
|
entity |
| Predicate | earliestEvidenceOfUse |
P55558
|
FINISHED |
| Object | possibly Anglo-Saxon period |
—
|
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: possibly Anglo-Saxon period | Statement: [Nottingham cave system, earliestEvidenceOfUse, possibly Anglo-Saxon period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestEvidenceOfUse Context triple: [Nottingham cave system, earliestEvidenceOfUse, possibly Anglo-Saxon period]
-
A.
historicalPeriodOfFirstUse
chosen
Indicates the historical time period during which something was first used or came into use.
-
B.
locationOfEarlyUse
Indicates the place where something was first or among the earliest instances to be used or applied.
-
C.
firstHistoricalUse
Indicates that the subject entity represents the earliest known or recorded instance of the object entity being used or occurring in history.
-
D.
earliestCultEvidence
Indicates the earliest known archaeological or historical evidence for the existence of a particular cult or organized worship practice.
-
E.
earliestEvidenceSite
Indicates that the related site is the location where the earliest known evidence of the subject was found.
- 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_69e2ff254570819093d197b1900305ac |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:02 a.m.