Triple
T11572808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cielo Drive area, Los Angeles |
E274431
|
entity |
| Predicate | notableEraOfPublicAttention |
P8452
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Cielo Drive area, Los Angeles, notableEraOfPublicAttention, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEraOfPublicAttention Context triple: [Cielo Drive area, Los Angeles, notableEraOfPublicAttention, late 1960s]
-
A.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
B.
inceptionOfNotoriety
Indicates the point or event at which an entity first becomes widely known or gains significant public notoriety.
-
C.
notableEraNickname
Indicates the informal or popular nickname by which a particular historical era or period is commonly known.
-
D.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
E.
notableDuring
chosen
Indicates that something was especially prominent, active, or significant during a particular time period or event.
- 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.