Triple
T13228268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bedford Flag |
E314936
|
entity |
| Predicate | attributedDateRange |
P51921
|
FINISHED |
| Object | circa 1720–1730 |
—
|
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: circa 1720–1730 | Statement: [Bedford Flag, attributedDateRange, circa 1720–1730]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attributedDateRange Context triple: [Bedford Flag, attributedDateRange, circa 1720–1730]
-
A.
createdBetween
chosen
Indicates that something was created within a specified start and end time or date range.
-
B.
representsDateRange
Indicates that a subject is associated with, valid for, or applicable during a specific start-to-end date range.
-
C.
occurredBetween
Indicates that an event or action took place within the time interval defined by two temporal boundaries.
-
D.
recordedBetween
Indicates that an event or data item was recorded at a time that falls within a specified start and end time interval.
-
E.
chronologicallyBetween
Indicates that one event or time point occurs after a first reference point and before a second reference point in temporal order.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d3232d48190a3c792b025c596a6 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:21 p.m.