Triple
T36332994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Saarbrücken |
E894702
|
entity |
| Predicate | playedInTopTier |
P192816
|
FINISHED |
| Object | 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: Bundesliga | Statement: [1. FC Saarbrücken, playedInTopTier, Bundesliga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInTopTier Context triple: [1. FC Saarbrücken, playedInTopTier, Bundesliga]
-
A.
playsInTopTier
Indicates that an entity participates as a competitor in the highest-level division or league within a given sport or competitive system.
-
B.
participatedInTopDivision
chosen
Indicates that an entity has taken part in the highest competitive level or top-tier division of a given activity, league, or competition.
-
C.
hasTopLeagueTeam
Indicates that an entity possesses or is associated with a team that competes in the highest-level league of a given sport or competition.
-
D.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
E.
playedAtLevel
Indicates that an entity participated or performed in an activity, event, or game at a specified level of difficulty, competition, or hierarchy.
- 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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:09 p.m.