Triple
T33213761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | panelist on ESPN’s Around the Horn |
E850230
|
entity |
| Predicate | goalOnShow |
P95145
|
FINISHED |
| Object | accumulate points |
—
|
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: accumulate points | Statement: [panelist on ESPN’s Around the Horn, goalOnShow, accumulate points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOnShow Context triple: [panelist on ESPN’s Around the Horn, goalOnShow, accumulate points]
-
A.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
B.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
C.
panelGoal
chosen
Indicates that an entity serves as the intended objective, outcome, or purpose associated with a particular panel or panel-related process.
-
D.
goalAtEnd
Indicates that a particular goal or objective holds true or is achieved at the final state or endpoint of a process, sequence, or event.
-
E.
goalsFor
Indicates the number of goals scored by one participant or team in favor of a particular side or match context.
- 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_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:30 a.m.