Triple
T36518180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain Davis Cup team |
E900103
|
entity |
| Predicate | homeTieAdvantage |
P38899
|
FINISHED |
| Object | strong record on clay at home |
—
|
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: strong record on clay at home | Statement: [Spain Davis Cup team, homeTieAdvantage, strong record on clay at home]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTieAdvantage Context triple: [Spain Davis Cup team, homeTieAdvantage, strong record on clay at home]
-
A.
homeCourtAdvantageFor
Indicates that one party benefits from playing or competing on its own familiar venue or territory against another party.
-
B.
homeAdvantageType
Indicates the specific kind or category of advantage associated with playing at a home venue.
-
C.
homeIceAdvantageBasedOn
Indicates that the degree of home-ice advantage is determined or influenced by the specified factor or condition.
-
D.
tieInWith
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
-
E.
homeFieldAdvantageFor
chosen
Indicates that one entity benefits from playing or operating in its own familiar location or environment when facing the other entity.
- 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.