Triple
T37383880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rushden & Diamonds F.C. |
E928511
|
entity |
| Predicate | rapidRiseThrough |
P76921
|
FINISHED |
| Object | English football league system |
—
|
NE NERFINISHED |
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: English football league system | Statement: [Rushden & Diamonds F.C., rapidRiseThrough, English football league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rapidRiseThrough Context triple: [Rushden & Diamonds F.C., rapidRiseThrough, English football league system]
-
A.
risesSteeplyFrom
Indicates that one entity ascends sharply or abruptly upward starting from the position or level of another entity.
-
B.
expandedRapidly
Indicates that an entity’s size, scope, or intensity increased significantly within a short period of time.
-
C.
rushType
Indicates the kind or category of urgency associated with an action, request, or process.
-
D.
rapidRiseThroughLeagues
chosen
Indicates a subject quickly advancing through multiple competitive levels or divisions in a league system within a short period of time.
-
E.
roseToProminenceIn
Indicates the time or context in which an entity became widely recognized, influential, or notable.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.