Triple
T22960356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vale of Pewsey |
E570877
|
entity |
| Predicate | notablePeriodOfOccupation |
P41036
|
FINISHED |
| Object | prehistoric era |
—
|
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: prehistoric era | Statement: [Vale of Pewsey, notablePeriodOfOccupation, prehistoric era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodOfOccupation Context triple: [Vale of Pewsey, notablePeriodOfOccupation, prehistoric era]
-
A.
occupationPeriod
Indicates the time span during which an entity holds or held a particular occupation or role.
-
B.
timePeriodOfEarlierOccupation
Indicates that one entity specifies the time span during which another entity was previously occupied or held a position before a later occupation.
-
C.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
D.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
wasOccupiedDuring
Indicates that an entity was under the control, presence, or use of another entity throughout a specified time period.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:47 p.m.