Triple
T3146038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss National League |
E65765
|
entity |
| Predicate | hasRelegationRound |
P15100
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Swiss National League, hasRelegationRound, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelegationRound Context triple: [Swiss National League, hasRelegationRound, yes]
-
A.
hasRelegationTo
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
B.
hasRelegationPlayOff
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
-
C.
hasRound
chosen
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
D.
hasRelegationHistory
Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
-
E.
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.
- 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_69ad8582f564819088c27e1f96153938 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59797788190a8d71262888c5df0 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.