Triple
T15056970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oud-Heverlee Leuven |
E379520
|
entity |
| Predicate | promotedToTopTier |
P69707
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Oud-Heverlee Leuven, promotedToTopTier, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToTopTier Context triple: [Oud-Heverlee Leuven, promotedToTopTier, 2011]
-
A.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
-
B.
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.
-
C.
establishedAsTier
Indicates that one entity has been formally designated or set to operate at a particular tier or level within a defined hierarchy or system.
-
D.
couldBePromotedTo
Indicates a potential or eligibility for one entity to be advanced or elevated to a higher role, status, or position relative to another.
-
E.
promotedToCaptain
Indicates that an entity has been elevated in rank or position to the role or status of captain.
- 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.