Triple
T32808769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roller Hockey International |
E839087
|
entity |
| Predicate | usedPlayingSurface |
P58186
|
FINISHED |
| Object | sport court plastic tile |
—
|
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: sport court plastic tile | Statement: [Roller Hockey International, usedPlayingSurface, sport court plastic tile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPlayingSurface Context triple: [Roller Hockey International, usedPlayingSurface, sport court plastic tile]
-
A.
playsOnSurface
Indicates that an entity performs or engages in an activity while being in contact with or supported by a particular surface.
-
B.
usesSurface
chosen
Indicates that one entity employs or interacts with another entity as a surface or platform for its action or function.
-
C.
hasPlaySurfaceDimensions
Indicates the specific measurements or size characteristics that define the dimensions of a play surface.
-
D.
usesPlayingArea
Indicates that one entity makes use of a particular playing area as the space in which an activity or event takes place.
-
E.
targetSurface
Indicates the surface or area that an action, effect, or object is directed at or intended to impact.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:15 a.m.