Triple
T12584124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HY |
E300411
|
entity |
| Predicate | isWidelyRecognizedIn |
P69873
|
FINISHED |
| Object | Finnish higher education community |
—
|
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 higher education community | Statement: [HY, isWidelyRecognizedIn, Finnish higher education community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWidelyRecognizedIn Context triple: [HY, isWidelyRecognizedIn, Finnish higher education community]
-
A.
isWidelyKnown
chosen
Indicates that something is generally recognized or familiar to a large number of people.
-
B.
reconocidaPor
Indicates that an entity is recognized, acknowledged, or honored by another entity.
-
C.
haveInternationalRecognition
Indicates that an entity is formally acknowledged or accepted by the international community or by official bodies across multiple countries.
-
D.
hasNotableRecognitionFor
Indicates that an entity has received notable recognition, such as awards, honors, or distinctions, specifically for another entity or achievement.
-
E.
recognizedIn
Indicates that an entity is formally acknowledged, honored, or given recognition within a particular context, setting, or domain.
- 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.