Triple
T19405527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macksville Show |
E485446
|
entity |
| Predicate | hasTypicalVenueType |
P97819
|
FINISHED |
| Object | showground |
—
|
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: showground | Statement: [Macksville Show, hasTypicalVenueType, showground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalVenueType Context triple: [Macksville Show, hasTypicalVenueType, showground]
-
A.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
-
B.
formerTypicalVenue
Indicates that a location was once the usual or primary venue for an entity’s activities or events, but no longer serves in that typical role.
-
C.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
D.
typicalVenueSetting
chosen
Indicates the usual or characteristic type of venue or setting in which an event, activity, or interaction typically takes place.
-
E.
typicalVenues
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6257af68881908147beedc29ff64c |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:36 p.m.