Triple
T30130071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premier Division Central |
E765811
|
entity |
| Predicate | establishedAsFormat |
P135524
|
FINISHED |
| Object | 2018–19 season |
—
|
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: 2018–19 season | Statement: [Premier Division Central, establishedAsFormat, 2018–19 season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsFormat Context triple: [Premier Division Central, establishedAsFormat, 2018–19 season]
-
A.
currentFormatInUseSince
chosen
Indicates the point in time since which a particular format has been actively in use.
-
B.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
C.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
D.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
E.
definesFormatFor
Indicates that one entity specifies or establishes the format or structural pattern to be used by another entity.
- 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_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 7:15 p.m.