Triple
T12584116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HY |
E300411
|
entity |
| Predicate | usedInAbbreviationSystems |
P63320
|
FINISHED |
| Object | Finnish university abbreviations |
—
|
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: Finnish university abbreviations | Statement: [HY, usedInAbbreviationSystems, Finnish university abbreviations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAbbreviationSystems Context triple: [HY, usedInAbbreviationSystems, Finnish university abbreviations]
-
A.
isUsedInAbbreviation
Indicates that one entity functions as a shortened or abbreviated form of another entity.
-
B.
usedInAbbreviationMeaning
Indicates that something (typically a word, term, or symbol) is employed as part of the meaning or expansion of an abbreviation.
-
C.
usesAbbreviationIn
chosen
Indicates that an entity is referred to by an abbreviated form within a specified context, source, or representation.
-
D.
usedInCompoundNames
Indicates that one entity’s name is employed as a component within the compound name of another entity.
-
E.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:04 p.m.