Triple
T30948581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Kennet Avenue |
E788468
|
entity |
| Predicate | hasMajorExcavationDate |
P135239
|
FINISHED |
| Object | 1930s |
—
|
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: 1930s | Statement: [West Kennet Avenue, hasMajorExcavationDate, 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorExcavationDate Context triple: [West Kennet Avenue, hasMajorExcavationDate, 1930s]
-
A.
majorExcavationsDate
chosen
Indicates the date or time period when significant excavation activities were carried out on an entity.
-
B.
majorExcavationsBegan
Indicates that significant archaeological or construction excavation work was initiated at a particular time or for a particular project.
-
C.
laterExcavationDate
Indicates that one excavation event occurred at a later date than another excavation event.
-
D.
hasArchaeologicalExcavationsSince
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
-
E.
hasExcavationNumber
Indicates that an entity is associated with a specific excavation identifier assigned during an archaeological or similar dig.
- 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_69f224c180f88190ad177372ee02b7e2 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffe8ebe9fc8190b1934a3c4074370c |
completed | May 10, 2026, 2:09 a.m. |
| PD | Predicate disambiguation | batch_69ffe83a5de88190bed3e8bac86e8760 |
completed | May 10, 2026, 2:06 a.m. |
Created at: April 29, 2026, 8:53 p.m.