Triple
T23390841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usutu royal homestead |
E594012
|
entity |
| Predicate | residentialRole |
P111117
|
FINISHED |
| Object | principal Zulu royal residence |
—
|
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: principal Zulu royal residence | Statement: [Usutu royal homestead, residentialRole, principal Zulu royal residence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residentialRole Context triple: [Usutu royal homestead, residentialRole, principal Zulu royal residence]
-
A.
residentialProfile
Indicates the relationship between an entity and the characteristics or status of where and how it resides or is housed.
-
B.
houseRole
chosen
Indicates the functional role, purpose, or use that a house has within a given context or system.
-
C.
isResidential
Indicates that something is used or designated primarily for people to live in, rather than for commercial, industrial, or other non-living purposes.
-
D.
ownerOccupation
Indicates that the occupation or job role of an entity that owns something is being specified or described.
-
E.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
- 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_69e25d2754fc819085deea939bde60ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a49bdfec8190afa592c66660c279 |
completed | April 29, 2026, 6:26 a.m. |
| PD | Predicate disambiguation | batch_69f061dde2e481908308952f9c0d3c2e |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:36 p.m.