Triple
T7411652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barbour’s Bruce |
E171017
|
entity |
| Predicate | dateOfCompositionApproximate |
P64676
|
FINISHED |
| Object | c. 1370s |
—
|
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: c. 1370s | Statement: [Barbour’s Bruce, dateOfCompositionApproximate, c. 1370s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfCompositionApproximate Context triple: [Barbour’s Bruce, dateOfCompositionApproximate, c. 1370s]
-
A.
dateOfComposition
Indicates the calendar date or time period when a particular work was created or composed.
-
B.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
-
C.
probableCenturyOfComposition
Indicates the century in which something (typically a work or composition) was most likely created or written.
-
D.
circaComposition
chosen
Indicates that one entity was composed or created around, but not exactly on, the time associated with another entity.
-
E.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2a027148190bdb6a7940389e377 |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.