Triple
T32723406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Davis Cup team |
E836736
|
entity |
| Predicate | ITFRegion |
P96304
|
FINISHED |
| Object | Americas Zone |
—
|
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: Americas Zone | Statement: [United States Davis Cup team, ITFRegion, Americas Zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ITFRegion Context triple: [United States Davis Cup team, ITFRegion, Americas Zone]
-
A.
teamSportGoverningBodyRegion
chosen
Indicates the geographic region or jurisdiction within which a governing body oversees or regulates a particular team sport.
-
B.
ITURegion
Indicates the International Telecommunication Union (ITU) regional classification to which an entity (such as a location or station) belongs.
-
C.
iccRegion
Indicates that one entity is associated with, located in, or falls under the jurisdiction of a particular ICC (International Criminal Court) region.
-
D.
isRegion
Indicates that one entity functions as a geographic or administrative region associated with another entity.
-
E.
clubRegion
Indicates that a club is located in, associated with, or belongs to a particular geographic region.
- 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_69f6c8b484b48190b5c37ba1c3101056 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.