Triple
T3128061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden Hills, California |
E65343
|
entity |
| Predicate | hasNotableResidentType |
P1092
|
FINISHED |
| Object | entertainers |
—
|
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: entertainers | Statement: [Hidden Hills, California, hasNotableResidentType, entertainers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableResidentType Context triple: [Hidden Hills, California, hasNotableResidentType, entertainers]
-
A.
hasNotableResident
chosen
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
B.
hasNonHumanResident
Indicates that a place or location is inhabited or occupied by one or more non-human entities.
-
C.
hasNotablePersonRaisedHere
Indicates that a notable person spent their formative or upbringing years in the referenced place.
-
D.
hasNotablePersonBornHere
Indicates that a notable or distinguished person was born at the referenced place.
-
E.
notableCharacterType
Indicates that an entity is a notable or prominent example of a specified character type or role.
- 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_69ad8580c72481909672d37acf647893 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada546a6648190bc4bc3e599e6aa95 |
completed | March 8, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69ad9df62e548190b053e1478deed467 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.