Triple
T22367672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kayserispor |
E552950
|
entity |
| Predicate | professionalStatusLevel |
P19008
|
FINISHED |
| Object | top division |
—
|
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: top division | Statement: [Kayserispor, professionalStatusLevel, top division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: professionalStatusLevel Context triple: [Kayserispor, professionalStatusLevel, top division]
-
A.
hasProfessionalStatus
chosen
Indicates that an entity holds a particular professional standing, rank, or qualification within a field or occupation.
-
B.
professionalClass
Indicates that an entity belongs to, or is categorized within, a particular professional or occupational class.
-
C.
professionalStatusRestriction
Indicates a limitation or condition placed on someone’s professional role, eligibility, or activities.
-
D.
professionalBase
Indicates that one entity serves as the primary professional location, organization, or base of operations for another entity.
-
E.
professionalStandardFor
Indicates that something defines, specifies, or serves as an authoritative professional standard that another entity is expected to follow or comply with.
- 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_69e11e4affcc8190ba7c27d29062558d |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158017400819094ebf7f91c26a724 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:44 p.m.