Triple
T19622298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seattle Sounders (NASL) |
E471040
|
entity |
| Predicate | playedSurface |
P16157
|
FINISHED |
| Object | artificial turf (Kingdome) |
—
|
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: artificial turf (Kingdome) | Statement: [Seattle Sounders (NASL), playedSurface, artificial turf (Kingdome)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedSurface Context triple: [Seattle Sounders (NASL), playedSurface, artificial turf (Kingdome)]
-
A.
playsOnSurface
chosen
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
-
B.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
C.
playedUnder
Indicates that one person participated as a player on a team or in a context where another person served as their coach or manager.
-
D.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
E.
hasPlaySurfaceDimensions
Indicates the specific measurements or size characteristics that define the dimensions of a play surface.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e7949081908a89414ef899fa20 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.