Triple
T36332978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Saarbrücken |
E894702
|
entity |
| Predicate | countryPlayedIn |
P10863
|
FINISHED |
| Object | Germany |
E1728
|
NE FINISHED |
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: Germany | Statement: [1. FC Saarbrücken, countryPlayedIn, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryPlayedIn Context triple: [1. FC Saarbrücken, countryPlayedIn, Germany]
-
A.
hasPlayedInCountry
chosen
Indicates that an entity (typically a person or team) has participated in a game, match, or performance within a specified country.
-
B.
isPlayedIn
Indicates that an instance of a game, sport, or performance takes place within or is hosted at a particular location or venue.
-
C.
playsOrPlayedIn
Indicates that an entity participates or has participated as a performer or player in a particular event, production, team, or activity.
-
D.
alsoPlayedIn
Indicates that an entity (such as a person or performer) participated or appeared in another work, production, or context in addition to the one already referenced.
-
E.
endedInCountry
Indicates that an event, process, or entity’s existence or occurrence concluded within the boundaries of a specified country.
- F. None of above.
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_69f76e4dcf088190a6c3216c209cab52 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a03008316dc8190a9f6faf48d25a4f8 |
completed | May 12, 2026, 10:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a30666e08190b49fda5e72180700 |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a030023e66881909ea79f1365ab538a |
completed | May 12, 2026, 10:25 a.m. |
Created at: May 3, 2026, 4:09 p.m.