Triple
T1646551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Futsal Euro |
E35594
|
entity |
| Predicate | usesPlayingSurface |
P16157
|
FINISHED |
| Object | hard court |
—
|
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: hard court | Statement: [UEFA Futsal Euro, usesPlayingSurface, hard court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPlayingSurface Context triple: [UEFA Futsal Euro, usesPlayingSurface, hard court]
-
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.
hasPlayingMethod
Indicates that there is a specific way, technique, or method by which something is played or performed.
-
C.
paintingSurface
Indicates that one entity serves as the physical surface or material on which another entity is painted or depicted.
-
D.
playsOn
Indicates that one entity participates or performs on a particular team, platform, or medium.
-
E.
hasSurfaceGravity
Indicates that one entity possesses a specific gravitational acceleration at its surface, typically measured as the strength of gravity experienced at or near that 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaa0fbe984819084f8daee81ca9b67 |
completed | March 6, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69a907ce4dd881909168a1e99505d4ec |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.