Triple
T1553933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Picts (early period) |
E33156
|
entity |
| Predicate | endOfDistinctIdentity |
P30280
|
FINISHED |
| Object | 10th 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: 10th century | Statement: [Picts (early period), endOfDistinctIdentity, 10th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endOfDistinctIdentity Context triple: [Picts (early period), endOfDistinctIdentity, 10th century]
-
A.
canonicalOrderEnd
Indicates the point or boundary at which a defined canonical or standard ordering of elements, events, or components concludes.
-
B.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
C.
endOfActivity
Indicates that a particular activity has reached its completion or final point in time.
-
D.
endSignedBy
Indicates that a document, agreement, or message is concluded with the signature or identifying mark of a specified party.
-
E.
endEvent
Indicates that one event or process marks the termination or conclusion of another event or process.
- 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_69a885ee6db8819099502bc5ce8af881 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a9407aa20881909e747f247ccec642 |
completed | March 5, 2026, 8:36 a.m. |
Created at: March 4, 2026, 7:27 p.m.