Triple
T33991237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal County of Berkshire |
E871547
|
entity |
| Predicate | hasOfficialResidenceOfMonarch |
P91692
|
FINISHED |
| Object | Windsor Castle |
—
|
NE NERFINISHED |
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: Windsor Castle | Statement: [Royal County of Berkshire, hasOfficialResidenceOfMonarch, Windsor Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialResidenceOfMonarch Context triple: [Royal County of Berkshire, hasOfficialResidenceOfMonarch, Windsor Castle]
-
A.
monarchUsedAsResidence
Indicates that a monarch uses or has used a particular place as their residence.
-
B.
servedRoyalResidence
chosen
Indicates that an entity functioned as an official residence used by royalty.
-
C.
containsRoyalResidence
Indicates that a location includes or encompasses a residence used by royalty.
-
D.
otherOfficialResidence
Indicates that an entity has an additional, secondary official residence distinct from its primary official residence.
-
E.
officialRoyalResidenceSince
Indicates that a location has served as the formal royal residence of a specified royal person or house starting from a given point in time.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:50 a.m.