Triple
T1827001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volgograd Arena |
E40674
|
entity |
| Predicate | hasFieldDimensions |
P3645
|
FINISHED |
| Object | 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: 105 m x 68 m | Statement: [Volgograd Arena, hasFieldDimensions, 105 m x 68 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFieldDimensions Context triple: [Volgograd Arena, hasFieldDimensions, 105 m x 68 m]
-
A.
hasDimension
chosen
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
B.
hasStandardizedDimensions
Indicates that an entity conforms to a predefined, uniform set of measurements or size specifications.
-
C.
hasNationalDimension
Indicates that something possesses a scope, relevance, or impact at the level of a nation or entire country.
-
D.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
E.
hasDimensionsApprox
Indicates that an entity has physical dimensions that are known only approximately, rather than as exact measurements.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:32 p.m.