Triple
T36518157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain Davis Cup team |
E900103
|
entity |
| Predicate | ITFRankingType |
P12242
|
FINISHED |
| Object | Davis Cup Nations Ranking |
—
|
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: Davis Cup Nations Ranking | Statement: [Spain Davis Cup team, ITFRankingType, Davis Cup Nations Ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ITFRankingType Context triple: [Spain Davis Cup team, ITFRankingType, Davis Cup Nations Ranking]
-
A.
technicalRating
Indicates the level or quality of technical proficiency, complexity, or performance associated with an entity.
-
B.
rankingType
chosen
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
C.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
D.
formationRank
Indicates the hierarchical position or level an entity holds within a particular formation or organized group.
-
E.
capacityRank
Indicates the relative ordering of entities based on how much capacity (e.g., volume, throughput, or capability) they possess compared to others.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.