Triple
T26060040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Chesterford |
E657232
|
entity |
| Predicate | historicalPeriodNoted |
P561
|
FINISHED |
| Object | Roman Britain |
—
|
NE NERFINISHED |
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: Roman Britain | Statement: [Great Chesterford, historicalPeriodNoted, Roman Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalPeriodNoted Context triple: [Great Chesterford, historicalPeriodNoted, Roman Britain]
-
A.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
B.
notablePeriodOfInterest
Indicates a time span that is particularly significant or noteworthy in relation to the subject.
-
C.
historicalIntroductionPeriod
Indicates the time period during which something was first introduced or came into use in a historical context.
-
D.
historicalDocumentationPeriod
Indicates the time span during which something is documented or recorded in historical sources.
-
E.
notableEra
chosen
Indicates the historical period or era for which an entity is especially recognized or significant.
- 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_69ee5bbd788481909e22bd7153d0c037 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 26, 2026, 7:16 p.m.