Triple
T24700898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cliftonhill Stadium |
E611735
|
entity |
| Predicate | hasCoveredAreas |
P158714
|
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: [Cliftonhill Stadium, hasCoveredAreas, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoveredAreas Context triple: [Cliftonhill Stadium, hasCoveredAreas, yes]
-
A.
hasAreaOfCoverage
Indicates that an entity provides services, influence, or applicability within a specified geographic or conceptual region.
-
B.
hasProtectedAreaCoverage
Indicates that a specified portion or extent of an area falls within officially designated protected areas.
-
C.
hasBeenCoveredBy
Indicates that something has received coverage or treatment by another entity, such as being reported on, discussed, or addressed.
-
D.
mayCoverArea
Indicates that one entity is permitted or able to extend over, include, or encompass a specified spatial area.
-
E.
hasCoverage
Indicates that one entity provides insurance or protection coverage for another entity or subject.
- F. None of above. chosen
Provenance (4 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_69e2c4d76d148190b58ad612467149a5 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 18, 2026, 3:22 a.m.