Triple
T29295201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wexford F.C. |
E742806
|
entity |
| Predicate | seasonPromotedToPremierDivision |
P49149
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Wexford F.C., seasonPromotedToPremierDivision, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seasonPromotedToPremierDivision Context triple: [Wexford F.C., seasonPromotedToPremierDivision, 2016]
-
A.
managedPromotionToPremierLeagueWith
Indicates that one entity was responsible for managing or leading another entity to achieve promotion to the Premier League together.
-
B.
hasPromotionToTopDivisionFrom
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
-
C.
teamManagedToPromotion
chosen
Indicates that a team successfully achieved promotion to a higher level, league, or division.
-
D.
hasPromotionPlacesToPremierLeague
Indicates that a competition or league grants promotion spots that allow teams to move up to the Premier League.
-
E.
promotedChampionship
Indicates that an entity has been elevated or advanced to a higher-level championship or competitive division.
- 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_69f0912323c48190b9a24ef8cf359225 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 1:05 p.m.