Triple
T2869183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kensington Palace Gardens |
E63515
|
entity |
| Predicate | hasNotableOccupantType |
P21135
|
FINISHED |
| Object | billionaires |
—
|
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: billionaires | Statement: [Kensington Palace Gardens, hasNotableOccupantType, billionaires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableOccupantType Context triple: [Kensington Palace Gardens, hasNotableOccupantType, billionaires]
-
A.
hasNotableType
Indicates that an entity is associated with a specific notable category or type that characterizes its significance or role.
-
B.
hasNotableBearerOccupation
Indicates that an entity is associated with a notable person who holds a specific occupation.
-
C.
hasPrimaryOccupants
chosen
Indicates that certain entities are the main or principal occupants of another entity (such as a space, structure, or location).
-
D.
hasNotableOwner
Indicates that an entity is or has been owned by a person or organization considered notable or significant.
-
E.
hasNotableHost
Indicates that an entity is associated with a host who is particularly prominent, famous, or otherwise noteworthy.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfe15ff081908dd1dad62c292b2b |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.