Triple
T33213756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | panelist on ESPN’s Around the Horn |
E850230
|
entity |
| Predicate | showStructureRole |
P118631
|
FINISHED |
| Object | contestant-like debater |
—
|
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: contestant-like debater | Statement: [panelist on ESPN’s Around the Horn, showStructureRole, contestant-like debater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showStructureRole Context triple: [panelist on ESPN’s Around the Horn, showStructureRole, contestant-like debater]
-
A.
showsStructure
Indicates that one entity visually or conceptually presents the internal organization, arrangement, or composition of another entity.
-
B.
hasStructureRole
chosen
Indicates that an entity serves a specific functional or positional role within a larger structure or organizational arrangement.
-
C.
displayStructure
Indicates that one entity presents or reveals the internal organization, layout, or arrangement of another entity.
-
D.
displayRole
Indicates the role or position an entity holds in the context of how it is presented or shown in a display.
-
E.
operaStructureRole
Indicates the functional or narrative role that a structural element plays within an opera.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:30 a.m.