Triple
T17179633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norfolk House |
E416946
|
entity |
| Predicate | aristocraticResidenceFor |
P126635
|
FINISHED |
| Object | English nobility |
—
|
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: English nobility | Statement: [Norfolk House, aristocraticResidenceFor, English nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aristocraticResidenceFor Context triple: [Norfolk House, aristocraticResidenceFor, English nobility]
-
A.
servedRoyalResidence
Indicates that an entity functioned as an official residence used by royalty.
-
B.
containsRoyalResidence
Indicates that a location includes or encompasses a residence used by royalty.
-
C.
becameRoyalResidenceIn
Indicates that a place or building started serving as an official royal residence at a specified point in time.
-
D.
builtResidence
Indicates that one entity constructed or was responsible for constructing a residence for another entity or for itself.
-
E.
formerCapitalResidence
Indicates that an entity once served as the official residence associated with a capital (such as a capital city or seat of government) but no longer holds that status.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc10afb48190a71f4a46f0280a14 |
completed | April 18, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e39c2fedb881908bfed2c3e5f2616a |
completed | April 18, 2026, 2:58 p.m. |
Created at: April 10, 2026, 5:37 a.m.