Triple
T38064063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sha Tin Racecourse |
E950422
|
entity |
| Predicate | hasInfieldAreaUse |
P151016
|
FINISHED |
| Object | additional training and equestrian facilities |
—
|
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: additional training and equestrian facilities | Statement: [Sha Tin Racecourse, hasInfieldAreaUse, additional training and equestrian facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInfieldAreaUse Context triple: [Sha Tin Racecourse, hasInfieldAreaUse, additional training and equestrian facilities]
-
A.
hasCurrentUseOfArea
Indicates that a specified area is presently being used for a particular purpose or activity.
-
B.
hasCentralAreaUse
Indicates that an entity’s central area is used or designated for a particular function or purpose.
-
C.
infieldUse
chosen
Indicates that something is used or applied within a specific field, area, or domain.
-
D.
hasDayUseArea
Indicates that a location or facility includes an area designated for daytime, non-overnight public use.
-
E.
hasInfield
Indicates that an entity possesses or includes a designated infield area, typically within a larger spatial or structural context.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
Created at: May 3, 2026, 4:21 p.m.