Triple
T5312727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacup Britannia Morris Men |
E119071
|
entity |
| Predicate | hasPerformanceSeason |
P1014
|
FINISHED |
| Object | Easter period |
—
|
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: Easter period | Statement: [Bacup Britannia Morris Men, hasPerformanceSeason, Easter period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceSeason Context triple: [Bacup Britannia Morris Men, hasPerformanceSeason, Easter period]
-
A.
performsSeason
Indicates that an entity carries out or executes a particular season of an activity, event, or series.
-
B.
hasNotablePerformanceIn
Indicates that an entity delivered a significant or distinguished performance within a specified work, event, or context.
-
C.
hasSeason
chosen
Indicates that an entity possesses, occurs during, or is associated with a particular season or set of seasons.
-
D.
hasRegularSeason
Indicates that an entity (such as a league, competition, or sport) includes or is associated with a defined regular season phase of play.
-
E.
hasNotablePerformance
Indicates that an entity has delivered a performance that is distinguished, remarkable, or otherwise noteworthy in a particular 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_69bd446b57bc8190a513d2e6c40314f3 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:54 p.m.