Triple
T3766894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National League |
E82699
|
entity |
| Predicate | featuresClubs |
P50991
|
FINISHED |
| Object | professional clubs |
—
|
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: professional clubs | Statement: [National League, featuresClubs, professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresClubs Context triple: [National League, featuresClubs, professional clubs]
-
A.
featuresSwissClubs
Indicates that something includes or highlights Swiss clubs as part of its content, composition, or offering.
-
B.
featuresFranchise
Indicates that one entity includes or presents a particular franchise as part of its content, offering, or composition.
-
C.
eligibleClubs
Indicates that certain clubs meet the required criteria or conditions to qualify for a specified status, activity, or benefit.
-
D.
notableClub
Indicates that an entity is prominently associated with or recognized for membership in a particular club or organization.
-
E.
otherProminentClub
Indicates a relationship where an entity is associated with another club that is also notable or high-profile, distinct from its primary or main club.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc0004608190a810ae0270ae2478 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.