Triple
T21128116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wedmore |
E520611
|
entity |
| Predicate | timePeriodOfKeyEvent |
P142951
|
FINISHED |
| Object | 9th 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: 9th century | Statement: [Wedmore, timePeriodOfKeyEvent, 9th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodOfKeyEvent Context triple: [Wedmore, timePeriodOfKeyEvent, 9th century]
-
A.
timePeriodEvent
Indicates that an event occurs, is scheduled, or is valid within a specified time period.
-
B.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
C.
keyShiftPeriod
Indicates the time interval during which a key (such as a cryptographic or access key) remains valid or is in active use before being changed or rotated.
-
D.
timePeriodFormulated
Indicates the time period during which something (such as a concept, theory, or plan) was formulated or developed.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- F. None of above. chosen
Provenance (4 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_69e0b50a623881909c0bbaf4f2c055e7 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7223a7a588190a01a66921b79b98b |
completed | April 21, 2026, 7:07 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 2:56 p.m.