Triple
T20876571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penny Lane, Liverpool |
E514030
|
entity |
| Predicate | notablePeriodOfInternationalFame |
P105129
|
FINISHED |
| Object | since 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: since late 1960s | Statement: [Penny Lane, Liverpool, notablePeriodOfInternationalFame, since late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePeriodOfInternationalFame Context triple: [Penny Lane, Liverpool, notablePeriodOfInternationalFame, since late 1960s]
-
A.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
B.
famousAt
Indicates that an entity is widely known or recognized in a particular place, context, or time.
-
C.
fameFor
Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
-
D.
gainedProminenceAs
Indicates that an entity became widely recognized or notable in the role, capacity, or identity specified by another entity.
-
E.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6767ec0819080721e2e75bd0d66 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.