Triple
T27753201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ebro Greyhound Park & Poker Room |
E701264
|
entity |
| Predicate | usedToOffer |
P22295
|
FINISHED |
| Object | live greyhound racing |
—
|
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: live greyhound racing | Statement: [Ebro Greyhound Park & Poker Room, usedToOffer, live greyhound racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedToOffer Context triple: [Ebro Greyhound Park & Poker Room, usedToOffer, live greyhound racing]
-
A.
usedAsOfferingAt
Indicates that something is employed or presented as an offering in a particular context, place, or event.
-
B.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
C.
usesOffering
Indicates that one entity makes use of, applies, or relies on a particular offering provided by another entity.
-
D.
offersWorksBy
Indicates that one entity makes works created by another entity available, such as for sale, display, or access.
-
E.
offering
chosen
Indicates that one entity presents or provides something to another entity, typically as a gift, contribution, or proposal.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 4:21 p.m.