Triple
T319256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philadelphia Eagles–New York Giants rivalry |
E7775
|
entity |
| Predicate | firstMeetingYear |
P12964
|
FINISHED |
| Object | 1933 |
—
|
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: 1933 | Statement: [Philadelphia Eagles–New York Giants rivalry, firstMeetingYear, 1933]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMeetingYear Context triple: [Philadelphia Eagles–New York Giants rivalry, firstMeetingYear, 1933]
-
A.
firstPlanStartYear
Indicates the calendar year in which an entity’s initial plan or planning period begins.
-
B.
firstSeriesYear
Indicates the year in which a series (such as a TV show, book series, or sports league season) first began or was initially released.
-
C.
firstMLSMeetingYear
Indicates the calendar year in which the entity had its first meeting or participation in Major League Soccer (MLS).
-
D.
designationYear
Indicates the year in which something was formally designated, assigned, or given an official status.
-
E.
negotiationStartYear
Indicates the calendar year in which a negotiation process between parties was initiated.
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e94513ec819089f5177f7a521e65 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2eb7c56bc8190ab787801af2eec8d |
completed | Feb. 28, 2026, 1:19 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.