Triple
T29622808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Good Friday Derby |
E755046
|
entity |
| Predicate | rivalryNameDerivedFrom |
P163890
|
FINISHED |
| Object | Good Friday holiday |
—
|
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: Good Friday holiday | Statement: [Good Friday Derby, rivalryNameDerivedFrom, Good Friday holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryNameDerivedFrom Context triple: [Good Friday Derby, rivalryNameDerivedFrom, Good Friday holiday]
-
A.
rivalryNamedAfter
chosen
Indicates that a rivalry between entities is named after a particular person, place, event, or concept.
-
B.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship between two entities.
-
C.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
D.
rivalryNameStyle
Indicates a stylistic or conventional way in which the name of a rivalry between entities is expressed or formatted.
-
E.
rivalNickname
Indicates that one entity uses or is known by a nickname specifically in the context of rivalry with another entity.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:35 p.m.