Triple
T7128292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wembley Park station |
E166120
|
entity |
| Predicate | eventManagement |
P75015
|
FINISHED |
| Object | queuing systems used on event days |
—
|
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: queuing systems used on event days | Statement: [Wembley Park station, eventManagement, queuing systems used on event days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eventManagement Context triple: [Wembley Park station, eventManagement, queuing systems used on event days]
-
A.
event
Indicates that there exists an occurrence or happening involving one or more entities, typically situated in time and possibly space.
-
B.
eventIn
Indicates that an event occurs within, or is situated in, a specific location, context, or larger event.
-
C.
eventName
Indicates the specific label or title assigned to identify an event within a system or context.
-
D.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
E.
eventEdition
Indicates a specific version or iteration of an event within a recurring or multi-edition series.
- F. None of above. chosen
Provenance (4 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_69c6888350588190870cd552b427a1cd |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e66b230c819090ddbc5396868305 |
completed | March 27, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c7289881909f3b533c384f9ed4 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:44 p.m.