Triple
T4741371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottingham Trent University |
E105249
|
entity |
| Predicate | hasQSStarsRating |
P43219
|
FINISHED |
| Object | 5-star overall rating |
—
|
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: 5-star overall rating | Statement: [Nottingham Trent University, hasQSStarsRating, 5-star overall rating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQSStarsRating Context triple: [Nottingham Trent University, hasQSStarsRating, 5-star overall rating]
-
A.
hasStarOn
Indicates that one entity bears or displays a star symbol positioned on another entity.
-
B.
starCount
Indicates the number of stars associated with an entity, typically representing a rating, quality level, or count of starred items.
-
C.
hasHighRatingOn
Indicates that one entity is evaluated or reviewed on another entity’s platform or system with a rating that meets or exceeds a defined high threshold.
-
D.
isFiveStarRank
chosen
Indicates that an entity holds or is assigned a five-star rank or rating within a given ranking system.
-
E.
hasBrightStar
Indicates that one entity possesses, contains, or is associated with a star characterized by high brightness.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64a5f3548190a6acf1dcfd64d11d |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.