Triple
T35795717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1938 Swiss Grand Prix |
E1034823
|
entity |
| Predicate | contestedByTeam |
P38351
|
FINISHED |
| Object | Mercedes-Benz |
—
|
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: Mercedes-Benz | Statement: [1938 Swiss Grand Prix, contestedByTeam, Mercedes-Benz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestedByTeam Context triple: [1938 Swiss Grand Prix, contestedByTeam, Mercedes-Benz]
-
A.
teamContestedBy
chosen
Indicates that a team participates as a competitor or contestant in a particular event, match, or competition.
-
B.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
-
C.
contestedByClub
Indicates that a club challenges, disputes, or opposes something, such as a decision, claim, or outcome.
-
D.
contestedByClubFrom
Indicates that a competition, match, or event is participated in or challenged by a club originating from a specified place or organization.
-
E.
antagonisticTeam
Indicates a relationship where two teams are in active opposition or conflict with each other.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.