Triple
T29622814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Friday Derby |
E755046
|
entity |
| Predicate | fixturePattern |
P167521
|
FINISHED |
| Object | alternating home advantage between clubs |
—
|
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: alternating home advantage between clubs | Statement: [Good Friday Derby, fixturePattern, alternating home advantage between clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixturePattern Context triple: [Good Friday Derby, fixturePattern, alternating home advantage between clubs]
-
A.
fixtureType
Indicates the specific kind or category of fixture associated with an entity or context.
-
B.
furPattern
Indicates the type or arrangement of fur markings or coloration that characterizes an entity’s coat.
-
C.
flagPattern
Indicates that one entity has a flag whose design or pattern matches or represents the other entity.
-
D.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
E.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e263460819086f937487b3187b2 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 28, 2026, 6:35 p.m.