Triple
T32723442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Davis Cup team |
E836736
|
entity |
| Predicate | hasDoublesPlayers |
P141531
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United States Davis Cup team, hasDoublesPlayers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDoublesPlayers Context triple: [United States Davis Cup team, hasDoublesPlayers, true]
-
A.
hasDoublesPartner
Indicates that one entity serves as the doubles partner of another in a paired or team-based activity or sport.
-
B.
hasMixedDoublesEquivalent
Indicates that one entity corresponds to or serves as the mixed doubles counterpart or equivalent of another entity.
-
C.
activeInDoubles
chosen
Indicates that an entity participates competitively in doubles events or matches.
-
D.
hasHomeDualsAt
Indicates that an entity has corresponding dual (home/away or counterpart) versions located at a specified place or context.
-
E.
supportsDualPlayfield
Indicates that an entity is capable of handling or displaying two playfields or gameplay areas simultaneously.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:11 a.m.