Triple
T16748636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CWTS Leiden |
E407017
|
entity |
| Predicate | typeOfRankingProduced |
P12242
|
FINISHED |
| Object | non-composite indicator ranking |
—
|
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: non-composite indicator ranking | Statement: [CWTS Leiden, typeOfRankingProduced, non-composite indicator ranking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRankingProduced Context triple: [CWTS Leiden, typeOfRankingProduced, non-composite indicator ranking]
-
A.
typeOfRankingEvent
Indicates the specific kind or category of ranking-related event that is being referred to.
-
B.
rankingType
chosen
Indicates the specific basis or method by which items are ordered or ranked relative to one another.
-
C.
producedRank
Indicates that one entity generated or assigned a specific rank or ordered position to another entity.
-
D.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
E.
rankType
Indicates the specific category or classification of a rank within a ranking or hierarchy system.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa2532ac81908e5ee5148e35f92e |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319cbd79c8190a03587a61c18bec0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.