Triple
T3335630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changing of the Guard |
E70133
|
entity |
| Predicate | traditionSinceCentury |
P20068
|
FINISHED |
| Object | 17th 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: 17th century | Statement: [Changing of the Guard, traditionSinceCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionSinceCentury Context triple: [Changing of the Guard, traditionSinceCentury, 17th century]
-
A.
traditionSince
Indicates that a tradition has been continuously practiced or recognized starting from a specified point in time.
-
B.
celebratedSinceCentury
chosen
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
C.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
D.
traditionInheritedFrom
Indicates that a tradition has been passed down or derived from an earlier source, group, or culture.
-
E.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb197bd0481909a5cf7eab386e176 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.