Triple
T24284735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caster Semenya |
E605638
|
entity |
| Predicate | filedAppealTo |
P10643
|
FINISHED |
| Object | Court of Arbitration for Sport |
—
|
NE NERFINISHED |
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: Court of Arbitration for Sport | Statement: [Caster Semenya, filedAppealTo, Court of Arbitration for Sport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filedAppealTo Context triple: [Caster Semenya, filedAppealTo, Court of Arbitration for Sport]
-
A.
appeal
chosen
Indicates that one party formally requests a higher authority to review, reconsider, or overturn a prior decision, judgment, or outcome.
-
B.
levelOfAppeal
Indicates the degree or intensity to which something is attractive, interesting, or desirable to someone or something.
-
C.
appealsFrom
Indicates that a decision, judgment, or ruling is being challenged and taken to a higher authority or court for review.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
hearsAppealTo
Indicates that one entity formally reviews and considers an appeal submitted by another 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f54c5948190a28207d47d6205e4 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.