Triple
T19325931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1. FC Heidenheim |
E483350
|
entity |
| Predicate | foundedAsIndependentFootballClub |
P115295
|
FINISHED |
| Object | 2007 |
—
|
LITERAL 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: 2007 | Statement: [1. FC Heidenheim, foundedAsIndependentFootballClub, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsIndependentFootballClub Context triple: [1. FC Heidenheim, foundedAsIndependentFootballClub, 2007]
-
A.
foundedAsIndependentClub
chosen
Indicates that an organization or team was originally established as an independent club, not as part of another entity or larger organization.
-
B.
foundedAsClub
Indicates that an organization or entity was originally established in the form of a club.
-
C.
foundedAsClubInYear
Indicates that an organization was originally established as a club in the specified year.
-
D.
foundedAsTopLevelClub
Indicates that an organization was originally established directly as a top-tier club, rather than being promoted or restructured from a lower level.
-
E.
foundedAsProfessionalClub
Indicates that an organization or team was originally established as a professional club rather than as an amateur or non-professional entity.
- 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_69d8e8d13e3c81909d91d1d5ec37c095 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d8bb28c81909b3a3bbb96b69b4f |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:33 p.m.