Triple
T27726582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pink Museum, Liverpool |
E697314
|
entity |
| Predicate | hostedSessionBy |
P43094
|
FINISHED |
| Object | Supersonic |
—
|
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: Supersonic | Statement: [The Pink Museum, Liverpool, hostedSessionBy, Supersonic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedSessionBy Context triple: [The Pink Museum, Liverpool, hostedSessionBy, Supersonic]
-
A.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
B.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
C.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
D.
hostedFirst
Indicates that one entity acted as the initial host for another entity, preceding any subsequent hosts.
-
E.
sessionOf
chosen
Indicates that one entity is a session that belongs to, occurs within, or is associated with another entity (such as an event, course, or meeting series).
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 3:09 p.m.