Triple
T25597948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albury Sports Ground |
E641705
|
entity |
| Predicate | hasSpectatorUse |
P138016
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Albury Sports Ground, hasSpectatorUse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpectatorUse Context triple: [Albury Sports Ground, hasSpectatorUse, yes]
-
A.
spectatorUse
chosen
Indicates that an entity observes or experiences an event, activity, or object without directly participating in or interacting with it.
-
B.
hasSpectatorType
Indicates that an event or activity is associated with a particular category or type of spectator.
-
C.
hasSpectatorArea
Indicates that a location or facility includes a designated area intended for spectators to observe an event or activity.
-
D.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
-
E.
hasSpectatorAmenities
Indicates that a place or facility provides amenities or features intended for the comfort or convenience of spectators.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 4:29 p.m.