Triple
T36846732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Stand |
E910567
|
entity |
| Predicate | relativeImportanceInStadium |
—
|
GENERATED |
| Object | one of the main spectator sections |
—
|
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: relativeImportanceInStadium Context triple: [Amsterdam Stand, relativeImportanceInStadium, one of the main spectator sections]
-
A.
relativeImportanceToTeam2
Indicates the comparative level of importance or value that one entity has relative to another within the context of a team.
-
B.
relativeImportanceToTeam1
Indicates the degree to which something is considered important or valuable to Team 1 relative to other things.
-
C.
importanceInLeague
Indicates the level of significance or prominence an entity holds within a particular league or competitive organization.
-
D.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
E.
relativeImportanceInFleet
Indicates the comparative significance or priority of an entity within the context of a fleet.
- F. None of above. chosen
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_69f76e7f65a881908651b702da592b6d |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.