Triple
T3146047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss National League |
E65765
|
entity |
| Predicate | featuresSwissClubs |
P46359
|
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, featuresSwissClubs, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSwissClubs Context triple: [Swiss National League, featuresSwissClubs, yes]
-
A.
featuresFranchise
Indicates that one entity includes or presents a particular franchise as part of its content, offering, or composition.
-
B.
featuresCanton
Indicates that an administrative region or entity includes or is associated with a specific canton as one of its subdivisions or components.
-
C.
stadiumFeature
Indicates that a stadium possesses or includes a particular feature, characteristic, or facility.
-
D.
eligibleClubs
Indicates that certain clubs meet the required criteria or conditions to qualify for a specified status, activity, or benefit.
-
E.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ada148e9108190b363dd0f1a94ac8e |
completed | March 8, 2026, 4:18 p.m. |
Created at: March 8, 2026, 3:05 p.m.