Triple
T32439896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usermaatre Setepenamun |
E828984
|
entity |
| Predicate | associatedWithRoyalResidence |
P57456
|
FINISHED |
| Object | Bubastis |
E29489
|
NE 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: Bubastis | Statement: [Usermaatre Setepenamun, associatedWithRoyalResidence, Bubastis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRoyalResidence Context triple: [Usermaatre Setepenamun, associatedWithRoyalResidence, Bubastis]
-
A.
containsRoyalResidence
Indicates that a location includes or encompasses a residence used by royalty.
-
B.
servedRoyalResidence
Indicates that an entity functioned as an official residence used by royalty.
-
C.
associatedWithPalace
chosen
Indicates a relationship where an entity has a connection, link, or involvement with a palace, such as through location, function, ownership, or affiliation.
-
D.
aristocraticResidenceFor
Indicates that one entity serves as the residence or dwelling specifically designated for an aristocratic person or group.
-
E.
hasNearbyRoyalResidence
Indicates that one entity has a royal residence located in close physical proximity to it.
- F. None of above.
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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a346674c3948190b48f53a2d3ca791d |
completed | June 18, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:55 a.m.