Triple
T28825460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITF Beach Tennis Tour |
E727888
|
entity |
| Predicate | rankingBody |
P175245
|
FINISHED |
| Object | International Tennis Federation |
—
|
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: International Tennis Federation | Statement: [ITF Beach Tennis Tour, rankingBody, International Tennis Federation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankingBody Context triple: [ITF Beach Tennis Tour, rankingBody, International Tennis Federation]
-
A.
rankingScope
Indicates the context or domain within which a ranking is defined, interpreted, or applied.
-
B.
rankingType
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
C.
rankingBasis
Indicates the criterion or standard used to determine the order or rank of entities in a ranking.
-
D.
rankingBehind
Indicates that one entity holds a lower or later position than another in an ordered ranking or hierarchy.
-
E.
rankedBy
Indicates that one entity is ordered or assigned a position in a hierarchy or list according to criteria determined or applied by another entity.
- F. None of above. chosen
Provenance (4 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 6:35 a.m.