Triple
T16322813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kissing Coppers |
E396339
|
entity |
| Predicate | firstInstalledOn |
P3054
|
FINISHED |
| Object | the wall of the Prince Albert pub in Brighton |
—
|
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: the wall of the Prince Albert pub in Brighton | Statement: [Kissing Coppers, firstInstalledOn, the wall of the Prince Albert pub in Brighton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstInstalledOn Context triple: [Kissing Coppers, firstInstalledOn, the wall of the Prince Albert pub in Brighton]
-
A.
dateInstalled
Indicates the specific date on which an item, system, or component was installed or put into service.
-
B.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
installedAt
chosen
Indicates that something has been set up, placed, or put into operation at a specific location or site.
-
D.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
firstShippedOn
Indicates the date on which something was initially shipped or dispatched for the first time.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b82fe88190a448597b7827f859 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.