Triple
T21764693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teleroboxer |
E537246
|
entity |
| Predicate | hasHUD |
P36451
|
FINISHED |
| Object | boxing match interface |
—
|
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 match interface | Statement: [Teleroboxer, hasHUD, boxing match interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHUD Context triple: [Teleroboxer, hasHUD, boxing match interface]
-
A.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
-
B.
hasScreen
chosen
Indicates that an entity is equipped with or includes a screen or display component.
-
C.
hasHaiden
Indicates that something possesses or includes a haiden, typically a worship or prayer hall associated with a shrine.
-
D.
hasVisuals
Indicates that one entity includes, displays, or is associated with visual elements or imagery related to another entity.
-
E.
hasHCR
Indicates that an entity possesses, is associated with, or is governed by a specific Health Care Regulation (HCR).
- 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.