Triple
T28322910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SV Sandhausen |
E717325
|
entity |
| Predicate | hasCompetedInLeague |
P136015
|
FINISHED |
| Object | 2. Bundesliga |
—
|
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: 2. Bundesliga | Statement: [SV Sandhausen, hasCompetedInLeague, 2. Bundesliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCompetedInLeague Context triple: [SV Sandhausen, hasCompetedInLeague, 2. Bundesliga]
-
A.
hasExperienceInLeague
Indicates that an entity has previously participated or been involved in a particular league.
-
B.
regionCompetedIn
Indicates the geographic region or area where an entity participated in a competition or contest.
-
C.
competedWithLeague
Indicates that an entity engaged in competitive activities or rivalry against a particular sports league.
-
D.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
E.
teamPlayedInLeague
chosen
Indicates that a particular team participated in and competed within a specified league.
- 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: April 28, 2026, 12:26 a.m.