Triple
T22682014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Derby |
E560504
|
entity |
| Predicate | fanSegregation |
P15323
|
FINISHED |
| Object | strictly enforced |
—
|
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: strictly enforced | Statement: [Eternal Derby, fanSegregation, strictly enforced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanSegregation Context triple: [Eternal Derby, fanSegregation, strictly enforced]
-
A.
hasHomeFansOnlySegregation
Indicates that only home-team supporters are allowed in a given area or event, with away fans excluded or segregated elsewhere.
-
B.
segregatedFor
Indicates that one entity is separated or set apart from others specifically for the use, benefit, or association of another entity.
-
C.
segregationBasis
chosen
Indicates the criterion or characteristic used as the basis for separating or distinguishing one group or set from another.
-
D.
segregatedIn
Indicates that one entity is separated or isolated within a specific space, group, or context defined by another entity.
-
E.
factionSplit
Indicates that a previously unified group has divided into separate, often opposing, factions.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1786113a881908f60285054d7ecfb |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62a6245881909506ff502da14137 |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:12 p.m.