Triple
T21764704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleroboxer |
E537246
|
entity |
| Predicate | playArea |
P85056
|
FINISHED |
| Object | boxing ring |
—
|
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: boxing ring | Statement: [Teleroboxer, playArea, boxing ring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playArea Context triple: [Teleroboxer, playArea, boxing ring]
-
A.
usesPlayingArea
chosen
Indicates that one entity makes use of a particular playing area as the space in which an activity or event takes place.
-
B.
hasPlayAreaType
Indicates the specific kind or category of play area associated with an entity (e.g., indoor, outdoor, playground type).
-
C.
settingWithinPlay
Indicates that a particular setting (such as a location or environment) occurs within and is part of a specific play.
-
D.
gamingSpace
Indicates a relationship where a space, area, or environment is designated or used specifically for gaming activities.
-
E.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a8a7f08190a4e50ebc24219585 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:51 p.m.