Triple

T24560946
Position Surface form Disambiguated ID Type / Status
Subject Gjøvik University College E607649 entity
Predicate hadStaffSize P23565 FINISHED
Object approximately 300 employees (around time of merger) 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: approximately 300 employees (around time of merger) | Statement: [Gjøvik University College, hadStaffSize, approximately 300 employees (around time of merger)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadStaffSize
Context triple: [Gjøvik University College, hadStaffSize, approximately 300 employees (around time of merger)]
  • A. staffSize chosen
    Indicates the number of staff members associated with an entity.
  • B. hadStaffRole
    Indicates that an entity served in a specific staff role or position for another entity during some period.
  • C. hadNumberOfMembers
    Indicates that an entity possessed or was associated with a specific count of members at a given time or in a given context.
  • D. hasEmployees
    Indicates that one entity employs one or more other entities as its workers or staff.
  • E. hasGeneralStaff
    Indicates that an entity has, is associated with, or is served by a general staff body responsible for overall strategic or administrative functions.
  • 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_69e2c4cc35a48190990b7571bc086df8 completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f63a348190a3c9fd96e3ad80b0 completed April 30, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69f2a6b99e7c8190ba7e2dc8729a314a completed April 30, 2026, 12:47 a.m.
Created at: April 18, 2026, 2:28 a.m.