Triple
T30130074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Division Central |
E765811
|
entity |
| Predicate | typicalClubStatus |
P201943
|
FINISHED |
| Object | semi-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: semi-professional clubs | Statement: [Premier Division Central, typicalClubStatus, semi-professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClubStatus Context triple: [Premier Division Central, typicalClubStatus, semi-professional clubs]
-
A.
traditionalClubStatus
Indicates that an entity holds a recognized, historically established status as a traditional club within a given context or organization.
-
B.
typicalStatus
chosen
Indicates the usual or standard state or condition that an entity normally has or occupies.
-
C.
clubStatus
Indicates the current standing or role an entity holds within a club, such as membership level, activity state, or official position.
-
D.
typicalVenueState
Indicates the usual or characteristic state or condition that a venue is in during the occurrence of an event or activity.
-
E.
clubState
Indicates that a club is associated with, based in, or officially belongs to a particular state or regional jurisdiction.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:15 p.m.