Triple
T32408548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royals |
E828149
|
entity |
| Predicate | foundedAsReadingRoyals |
P146889
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Royals, foundedAsReadingRoyals, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsReadingRoyals Context triple: [Royals, foundedAsReadingRoyals, 2001]
-
A.
foundedAsRoyalsYear
chosen
Indicates the year in which an entity was originally founded under the name "Royals."
-
B.
lastRoyalHouseFounded
Indicates that one entity is the most recently established royal house associated with another entity (such as a country, realm, or dynasty sequence).
-
C.
royalHouseFounder
Indicates that one entity is the person who founded or established the royal house or dynasty to which the other entity belongs.
-
D.
existedAsRoyalCourtFrom
Indicates that an entity functioned as a royal court during a specified time period.
-
E.
createdDukeOfRichmondBy
Indicates the act by which an authority formally established or conferred the title of Duke of Richmond upon a person.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 12:53 a.m.