Triple
T24534177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coronation Street exterior set |
E606898
|
entity |
| Predicate | firstUsedForSeries |
P6318
|
FINISHED |
| Object | Coronation Street |
—
|
NE NERFINISHED |
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: Coronation Street | Statement: [Coronation Street exterior set, firstUsedForSeries, Coronation Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedForSeries Context triple: [Coronation Street exterior set, firstUsedForSeries, Coronation Street]
-
A.
firstUsedFor
chosen
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
-
B.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
C.
firstUsedBy
Indicates that something was initially utilized, applied, or employed by a particular entity before any others.
-
D.
firstUsedInEvent
Indicates that something (such as an object, method, or concept) was used for the first time during a specified event.
-
E.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.