Triple
T15056972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oud-Heverlee Leuven |
E379520
|
entity |
| Predicate | returnedToTopTier |
P69707
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Oud-Heverlee Leuven, returnedToTopTier, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToTopTier Context triple: [Oud-Heverlee Leuven, returnedToTopTier, 2015]
-
A.
reintroducedAsTier
Indicates that something has been brought back or reinstated in a system or structure as a specific tier or level.
-
B.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
C.
returnedToTeam
Indicates that an individual who was previously away has come back to rejoin the same team.
-
D.
topTierUntil
Indicates that an entity holds a top-tier or highest-status position only up to a specified point in time, after which this status no longer applies.
-
E.
promotedBackToTopFlight
chosen
Indicates that an entity has been moved back up from a lower division or level to the highest (top-flight) tier in a competitive hierarchy.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda937f788190899d81bbb2084443 |
completed | April 15, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:01 a.m.