Triple
T25044291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France Davis Cup team |
E627191
|
entity |
| Predicate | DavisCupRunnerUpFinishes |
P123831
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [France Davis Cup team, DavisCupRunnerUpFinishes, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DavisCupRunnerUpFinishes Context triple: [France Davis Cup team, DavisCupRunnerUpFinishes, 9]
-
A.
DavisCupFinalAppearances
chosen
Indicates the number of times an entity has reached the final round of the Davis Cup tennis competition.
-
B.
davisCupTitle
Indicates that the subject has won a Davis Cup tennis title, specifying a championship victory in the Davis Cup competition.
-
C.
runnerUpFinishesAtUsOpen
Indicates that an entity finished in second place (as runner-up) at the US Open in a given event or year.
-
D.
FedCupChampionWith
Indicates that two entities are connected by having won the Fed Cup together as part of the same championship team.
-
E.
hasNationalRunnerUpFinishes
Indicates that an entity has achieved one or more second-place (runner-up) finishes in a national-level competition or championship.
- 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_69e2ff2b4c80819087c916b2b16241b9 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4530f26948190af6de16b9013815f |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:08 a.m.