Triple
T938329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulham F.C. |
E20246
|
entity |
| Predicate | promotion |
P8176
|
FINISHED |
| Object | promoted to Premier League 2000–01 |
—
|
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: promoted to Premier League 2000–01 | Statement: [Fulham F.C., promotion, promoted to Premier League 2000–01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: promotion Context triple: [Fulham F.C., promotion, promoted to Premier League 2000–01]
-
A.
promotionTo
chosen
Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
-
B.
promotionFrom
Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
-
C.
promotionBetween
Indicates a relationship where one entity advances or elevates another entity’s status, rank, or visibility relative to a previous state.
-
D.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
E.
promotionGimmick
Indicates a relationship where something is used as a special tactic or device to attract attention or boost interest in a promotion.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b29c68f48190aecad10e351a99de |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.