Triple
T8884780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ascot railway station |
E211500
|
entity |
| Predicate | isBusyDuring |
P85526
|
FINISHED |
| Object | Ascot Racecourse events |
—
|
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: Ascot Racecourse events | Statement: [Ascot railway station, isBusyDuring, Ascot Racecourse events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBusyDuring Context triple: [Ascot railway station, isBusyDuring, Ascot Racecourse events]
-
A.
isBusyLine
Indicates that a communication line or channel is currently in use and cannot accept additional connections or calls.
-
B.
usedInBusinessHours
Indicates that something is utilized or occurs during designated business operating hours.
-
C.
isBusiestInSystem
Indicates that an entity has the highest level of activity or load compared to all other entities within the same system.
-
D.
inSessionDuring
Indicates that an entity is actively engaged in or part of a session throughout a specified time period.
-
E.
hasWorkPeriod
Indicates that an entity is associated with a specific span of time during which it performs or is engaged in some work or activity.
- 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_69ca838f9e20819096ab1f236a70381a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc616cf8c48190a27b381e48f23377 |
completed | April 1, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5d6e54808190af4156edd4c8ffbc |
completed | March 31, 2026, 11:49 p.m. |
Created at: March 30, 2026, 6:53 p.m.