Triple
T4954152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selhurst Park |
E111239
|
entity |
| Predicate | hasPitchWidth |
P43595
|
FINISHED |
| Object | approximately 68 metres |
—
|
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: approximately 68 metres | Statement: [Selhurst Park, hasPitchWidth, approximately 68 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchWidth Context triple: [Selhurst Park, hasPitchWidth, approximately 68 metres]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasPitchType
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
-
C.
seatPitch
Indicates the distance between a seat and the seat directly in front of it, typically measuring legroom or spacing in a seating arrangement.
-
D.
pitchDimensions
chosen
Indicates the specific measurements or size parameters that define the extent or layout of a pitch or playing field.
-
E.
hasRetractablePitch
Indicates that an entity (typically a stadium or venue) possesses a playing surface or pitch that can be mechanically extended or withdrawn as needed.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b945c0819082723712905f8295 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:32 p.m.