Triple
T4675363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountfield HK |
E103665
|
entity |
| Predicate | foundedAsTopLevelClub |
P58952
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Mountfield HK, foundedAsTopLevelClub, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsTopLevelClub Context triple: [Mountfield HK, foundedAsTopLevelClub, 2013]
-
A.
foundedAsMajorLeagueClub
Indicates that an organization or team was originally established as a major league club at the time of its founding.
-
B.
associatedClubFounded
Indicates that there exists a club associated with an entity and specifies the date or time at which that associated club was founded.
-
C.
foundedAsTopDivision
Indicates that an organization, competition, or league was originally established as the highest (top) division within its hierarchical structure.
-
D.
foundedAsRepresentativeTeam
Indicates that an entity was established specifically to serve as a representative team for a larger group, organization, or region.
-
E.
teamFoundedAs
Indicates the original name or identity under which a team was first established or created.
- 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_69bd43dda32c8190938b37744ca270fc |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6217e0088190836570522e324dc6 |
completed | March 20, 2026, 3:04 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:15 p.m.