Triple
T13568182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rothesay International Eastbourne |
E324091
|
entity |
| Predicate | firstHeldAsCombinedEvent |
P110108
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Rothesay International Eastbourne, firstHeldAsCombinedEvent, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHeldAsCombinedEvent Context triple: [Rothesay International Eastbourne, firstHeldAsCombinedEvent, 2017]
-
A.
firstHeldAsSeparateEvent
Indicates that an event was, for the first time, organized and conducted as a distinct, standalone occurrence separate from other events.
-
B.
firstHeldAs
Indicates the initial time or context in which an entity was first possessed, owned, or held by another entity.
-
C.
firstHeldAsCentralizedEvent
Indicates that something was initially conducted as a centrally organized, unified event rather than in a distributed or local form.
-
D.
firstHeldAsNamedEvent
Indicates that an entity was first held or took place under a specific event name.
-
E.
firstHeldAt
Indicates the initial time or event at which an entity was first held, possessed, or hosted.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00e0188819094fde44f85adb69c |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf7fefa881908471f1400f813ccc |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:48 p.m.