Triple
T36518179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spain Davis Cup team |
E900103
|
entity |
| Predicate | formatParticipation |
P185806
|
FINISHED |
| Object | Davis Cup Finals |
—
|
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: Davis Cup Finals | Statement: [Spain Davis Cup team, formatParticipation, Davis Cup Finals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatParticipation Context triple: [Spain Davis Cup team, formatParticipation, Davis Cup Finals]
-
A.
participationStatus
Indicates the current state or condition of an entity’s involvement in an event, activity, or process (e.g., planned, active, completed, or cancelled participation).
-
B.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
C.
establishesParticipationIn
Indicates that one entity formally creates or defines another entity’s involvement in an activity, event, or group.
-
D.
estimatedParticipation
Indicates an approximate or predicted level, amount, or likelihood of an entity’s involvement in a given activity or event.
-
E.
resultOfParticipation
Indicates that something occurs or is produced as a consequence of an entity’s participation in an event or activity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.