Triple
T19294050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wimbledon F.C. |
E482513
|
entity |
| Predicate | promotedToTopFlight |
P135159
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Wimbledon F.C., promotedToTopFlight, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotedToTopFlight Context triple: [Wimbledon F.C., promotedToTopFlight, 1986]
-
A.
promotedBackToTopFlight
Indicates that an entity has been moved back up from a lower division or level to the highest (top-flight) tier in a competitive hierarchy.
-
B.
hasPromotionToTopDivisionFrom
Indicates that an entity gains promotion to the top division originating from the specified lower division or competition.
-
C.
promotedToCaptain
Indicates that an entity has been elevated in rank or position to the role or status of captain.
-
D.
promotedToRankBy
Indicates that an entity was elevated to a particular rank or position through the action or decision of another entity.
-
E.
promotedToReferee
Indicates that an entity has been elevated or advanced to the role or position of a referee.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc84500c81908ac53711335ad2d9 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:31 p.m.