Triple
T23291633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keighley Cougars |
E590045
|
entity |
| Predicate | hasEraOfSuccess |
P64303
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Keighley Cougars, hasEraOfSuccess, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEraOfSuccess Context triple: [Keighley Cougars, hasEraOfSuccess, 1990s]
-
A.
historicalEraOfSuccess
chosen
Indicates that an entity achieved notable success or prominence during a specified historical era.
-
B.
isHistoricallySuccessful
Indicates that an entity has achieved notable success or positive outcomes over a significant period in the past.
-
C.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
D.
hasNotableSuccessIn
Indicates that an entity has achieved significant or widely recognized success in a particular field, activity, or domain.
-
E.
hasBusinessAchievement
Indicates that an entity has attained a notable accomplishment, success, or milestone in a business or commercial context.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cb3fec8190a95255da97dd984e |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:02 p.m.