Triple
T29861050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burnett family |
E758315
|
entity |
| Predicate | centuriesAtCrathes |
P168201
|
FINISHED |
| Object | 16th–20th centuries |
—
|
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: 16th–20th centuries | Statement: [Burnett family, centuriesAtCrathes, 16th–20th centuries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuriesAtCrathes Context triple: [Burnett family, centuriesAtCrathes, 16th–20th centuries]
-
A.
centuriesOld
Indicates that something has existed or remained in existence for several hundred years.
-
B.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
C.
odiCenturies
Indicates the number of centuries a player has scored in One Day International (ODI) cricket matches.
-
D.
reignCenturyBCE
Indicates that a subject’s reign or rule occurred during a specified century before the Common Era (BCE).
-
E.
coveredSinceCentury
Indicates that one entity has been covered, coated, or kept under coverage continuously starting from a specified century.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67685c8c0819089a31631bfba0797 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 29, 2026, 5:49 p.m.