Triple
T19421555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisian handball |
E485866
|
entity |
| Predicate | playingAreaType |
P74153
|
FINISHED |
| Object | outdoor field |
—
|
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: outdoor field | Statement: [Frisian handball, playingAreaType, outdoor field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playingAreaType Context triple: [Frisian handball, playingAreaType, outdoor field]
-
A.
hasPlayAreaType
chosen
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
B.
arenaType
Indicates the specific kind or category of arena associated with an entity or event.
-
C.
spectatorAreaType
Indicates the specific kind or category of area designated for spectators in a venue or event setting.
-
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.
homeArenaType
Indicates the type or category of arena that serves as the primary home venue for an entity.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.