Triple
T34583738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1931 Schneider Trophy |
E887983
|
entity |
| Predicate | mainCompetitorNation |
P192671
|
FINISHED |
| Object | Italy |
—
|
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: Italy | Statement: [1931 Schneider Trophy, mainCompetitorNation, Italy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCompetitorNation Context triple: [1931 Schneider Trophy, mainCompetitorNation, Italy]
-
A.
primaryCompetitionCountry
Indicates the main country in which an entity primarily conducts or participates in competitive activities or markets.
-
B.
countryRivalClubs
Indicates that two sports clubs from the same country are considered rivals.
-
C.
rivalOf
Indicates a relationship in which two entities compete against or oppose each other, often seeking advantage in the same domain or objective.
-
D.
primaryOpposingCountry
Indicates that one country is the main or principal adversary or opponent of another country in a conflict, rivalry, or opposition.
-
E.
hostNationCompetitor
Indicates that the competitor is representing the nation that is hosting the event or competition.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 1, 2026, 2:03 a.m.