Triple
T49342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankees–Red Sox rivalry |
E969
|
entity |
| Predicate | fanCulture |
P897
|
FINISHED |
| Object | strong regional identities in New England and New York |
—
|
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: strong regional identities in New England and New York | Statement: [Yankees–Red Sox rivalry, fanCulture, strong regional identities in New England and New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanCulture Context triple: [Yankees–Red Sox rivalry, fanCulture, strong regional identities in New England and New York]
-
A.
genre
Indicates the artistic or thematic category to which a work (such as a book, film, or song) belongs.
-
B.
fareMedia
Indicates that a particular type of ticket, pass, or payment instrument is used as the medium for paying a fare.
-
C.
fanBase
chosen
Indicates that one entity is the group of admirers or supporters devoted to another entity.
-
D.
stars
Indicates that one entity marks, highlights, or designates another as special, important, or featured (often by assigning a star or similar marker).
-
E.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abfa7bc8190932c137a823efcb6 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.