Triple
T36679374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand |
E905633
|
entity |
| Predicate | hasRelativePositionToField |
—
|
GENERATED |
| Object | east touchline |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelativePositionToField Context triple: [East Stand, hasRelativePositionToField, east touchline]
-
A.
positionInField
Indicates the specific role, location, or functional placement an entity occupies within a defined field, domain, or area of activity.
-
B.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
C.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
inSameFieldAs
Indicates that two entities work, study, or specialize within the same professional or academic field.
-
E.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
- F. None of above.
Provenance (1 batch)
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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:12 p.m.