Triple
T38064075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sha Tin Sports Ground |
E950423
|
entity |
| Predicate | hasFootballPitch |
P89688
|
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: [Sha Tin Sports Ground, hasFootballPitch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFootballPitch Context triple: [Sha Tin Sports Ground, hasFootballPitch, yes]
-
A.
homeSoccerField
Indicates that a particular soccer field serves as the designated home field for a given team or organization.
-
B.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
C.
hasPitchSurface
Indicates that one entity possesses or is characterized by a particular pitch surface (e.g., a sloped or inclined surface).
-
D.
hasRugbyGround
Indicates that an entity possesses, contains, or is associated with a rugby ground as a facility or location.
-
E.
hasLocalFootballGround
chosen
Indicates that a place or organization possesses or is associated with a nearby football ground used for local matches or activities.
- 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_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 3, 2026, 4:21 p.m.