Triple
T18768951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VHL |
E458962
|
entity |
| Predicate | hasRelegationRelation |
P9667
|
FINISHED |
| Object | lower regional leagues |
—
|
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: lower regional leagues | Statement: [VHL, hasRelegationRelation, lower regional leagues]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelegationRelation Context triple: [VHL, hasRelegationRelation, lower regional leagues]
-
A.
hasRelegationTo
chosen
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
B.
hasRelegationHistory
Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
-
C.
hasRelation
Indicates that there exists some specified relationship or association between two entities.
-
D.
hasPromotionRelegation
Indicates that there is a system in which entities can move up (promotion) or down (relegation) between hierarchical levels based on defined criteria or performance.
-
E.
hasRelegationSpots
Indicates that a competition or league includes designated positions in its standings whose occupants will be relegated to a lower division or tier.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.