Triple
T4292174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillehammer FK |
E99619
|
entity |
| Predicate | languageOfClubAdministration |
P51016
|
FINISHED |
| Object | Norwegian |
—
|
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: Norwegian | Statement: [Lillehammer FK, languageOfClubAdministration, Norwegian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfClubAdministration Context triple: [Lillehammer FK, languageOfClubAdministration, Norwegian]
-
A.
languageOfClubMedia
Indicates the language in which a club’s media or communications are produced or presented.
-
B.
languageOfLocalOrganization
chosen
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
C.
languageOfCompetition
Indicates the language in which a competition is conducted or officially presented.
-
D.
historicallyDominantLanguageOfAdministrationIn
Indicates that a language has historically been the primary language used for official governance and administrative functions within a given place or political entity.
-
E.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3508035a08190b752c8edce0aff86 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fc4c0c8190a7fcd814e27308a5 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.