Triple
T23418275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tara Brooch |
E560572
|
entity |
| Predicate | dateEstimated |
P877
|
FINISHED |
| Object | 7th 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: 7th century | Statement: [Tara Brooch, dateEstimated, 7th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateEstimated Context triple: [Tara Brooch, dateEstimated, 7th century]
-
A.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
C.
estimatedStartDate
Indicates the date on which something is expected or planned to begin, based on current information or projections.
-
D.
areEstimatedIn
Indicates that a value or quantity is approximated or inferred within a specified context, framework, or unit.
-
E.
estimatedUsing
Indicates that one entity’s value, state, or outcome is derived by applying an estimation method, model, or procedure based on another entity.
- 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a5438ac08190a40a3d6402794699 |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:39 p.m.