Triple
T23840798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnish national ice hockey teams |
E590982
|
entity |
| Predicate | nicknameSharedElement |
P40775
|
FINISHED |
| Object | Leijonat (The Lions) |
—
|
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: Leijonat (The Lions) | Statement: [Finnish national ice hockey teams, nicknameSharedElement, Leijonat (The Lions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nicknameSharedElement Context triple: [Finnish national ice hockey teams, nicknameSharedElement, Leijonat (The Lions)]
-
A.
sharesGivenNameWith
Indicates that two entities have the same given (first) name.
-
B.
nicknameEmphasizes
Indicates that a nickname highlights or draws special attention to a particular characteristic, trait, or aspect of the entity it refers to.
-
C.
sharesElementsWith
chosen
Indicates that two entities have one or more elements or components in common.
-
D.
sharesAppearanceTraitWith
Indicates that two entities possess at least one similar or matching visual or appearance-related characteristic.
-
E.
sharesCharacterWith
Indicates that two entities have at least one character (such as a letter, symbol, or glyph) in common.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88797d4819081831fd3f8822ef4 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:08 p.m.