Triple
T25044420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davis Cup |
E627194
|
entity |
| Predicate | organizingHeadquartersLocation |
P33420
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [Davis Cup, organizingHeadquartersLocation, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizingHeadquartersLocation Context triple: [Davis Cup, organizingHeadquartersLocation, London]
-
A.
organizerHeadquartersLocation
chosen
Indicates the place where the main offices or central administrative base of the organizing entity are located.
-
B.
headquartersSuccessorOrganizationLocation
Indicates that the location served as the headquarters for a successor organization that followed a previous entity.
-
C.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
D.
headquartersLocationOfFoundedOrganization
Indicates that a location serves as the headquarters of an organization that was founded there.
-
E.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
- 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_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 18, 2026, 6:08 a.m.