Triple
T20744685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dock Green, East London |
E510547
|
entity |
| Predicate | portrayedTimePeriod |
P93599
|
FINISHED |
| Object | mid-20th-century London |
—
|
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: mid-20th-century London | Statement: [Dock Green, East London, portrayedTimePeriod, mid-20th-century London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portrayedTimePeriod Context triple: [Dock Green, East London, portrayedTimePeriod, mid-20th-century London]
-
A.
showsTimePeriod
Indicates that one entity presents or displays a specific span or interval of time associated with another entity.
-
B.
appearsInTimePeriod
Indicates that an entity is present, active, or occurs within a specified time period.
-
C.
appearsInTimePeriodDepicted
Indicates that something is present or occurs within the specific time period that is depicted or represented.
-
D.
portrayalDurationYears
Indicates the number of years an entity has continuously portrayed or represented another entity or role.
-
E.
settingDepictedPeriod
chosen
Indicates the historical or temporal period in which the setting of something (e.g., a work or scene) is depicted.
- 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c21197088190951a4c4a7e765891 |
completed | April 21, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:33 p.m.