Triple
T11821922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference National |
E281159
|
entity |
| Predicate | numberOfPromotedTeamsPerSeason |
P101686
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Conference National, numberOfPromotedTeamsPerSeason, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfPromotedTeamsPerSeason Context triple: [Conference National, numberOfPromotedTeamsPerSeason, 2]
-
A.
typicalRelegatedTeamsPerSeason
Indicates the usual or average number of teams that are relegated from a league in a single season.
-
B.
promotedClubsPerSeasonFromEFLChampionship
Indicates the relationship where clubs are promoted from the EFL Championship to a higher league in a given season.
-
C.
typicalNumberOfTopDivisionTeams
Indicates the usual or standard number of teams that compete in the highest-level division of a league or competition.
-
D.
hasNumberOfConferencesInLeague
Indicates the quantity of conferences that exist within a given league.
-
E.
totalMatchesPerSeason
Indicates the total number of matches associated with an entity within a single season.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.