Triple

T2183938
Position Surface form Disambiguated ID Type / Status
Subject Lund University E49107 entity
Predicate hasQSWorldRankingRange P13383 FINISHED
Object top 100–150 globally 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: top 100–150 globally | Statement: [Lund University, hasQSWorldRankingRange, top 100–150 globally]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasQSWorldRankingRange
Context triple: [Lund University, hasQSWorldRankingRange, top 100–150 globally]
  • A. hasWorldRankingPoints
    Indicates that an entity possesses a certain number of points in a global or international ranking system.
  • B. QSWorldUniversityRankingRange chosen
    Indicates the position of an institution within a specified range of ranks in the QS World University Rankings.
  • C. hasRankingUnit
    Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
  • D. TimesHigherEducationRankingRange
    Indicates that an entity’s position in the Times Higher Education ranking falls within a specified numerical range.
  • E. globalRanking
    Indicates the position or status of an entity relative to all comparable entities worldwide according to some ranking criteria.
  • 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_69a88aa72d348190a9544bb5b8a4e71d completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abbf9e99f08190892d34485c8f2f25 completed March 7, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69abbda32d1881909d1fd83a751fb21c completed March 7, 2026, 5:54 a.m.
Created at: March 4, 2026, 7:45 p.m.