Triple
T3989894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Douglas Park |
E86961
|
entity |
| Predicate | hasPitchDimensions |
P43595
|
FINISHED |
| Object | approximately 105 m x 68 m |
—
|
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 105 m x 68 m | Statement: [New Douglas Park, hasPitchDimensions, approximately 105 m x 68 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchDimensions Context triple: [New Douglas Park, hasPitchDimensions, approximately 105 m x 68 m]
-
A.
pitchDimensions
chosen
Indicates the specific measurements or size parameters that define the extent or layout of a pitch or playing field.
-
B.
hasNationalDimension
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
C.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
-
D.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
E.
hasStandardizedDimensions
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.