Triple
T8521813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rutgers–Lafayette football rivalry |
E201709
|
entity |
| Predicate | earliestGamesDecade |
P83134
|
FINISHED |
| Object | 1880s |
—
|
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: 1880s | Statement: [Rutgers–Lafayette football rivalry, earliestGamesDecade, 1880s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestGamesDecade Context triple: [Rutgers–Lafayette football rivalry, earliestGamesDecade, 1880s]
-
A.
firstGamesTraditionallyDated
Indicates that the subject’s earliest known or customary date of occurrence is based on traditional or conventional dating rather than precise historical evidence.
-
B.
screenDebutDecade
Indicates the decade during which an entity first appeared on screen (e.g., in film or television).
-
C.
developmentStartDecade
Indicates the decade during which the development or creation of an entity was initiated.
-
D.
releasedInDecade
Indicates that an item (such as a work, product, or event) was released during a specified ten-year time period.
-
E.
productionDecade
Indicates the decade during which something (such as a work, product, or item) was produced or created.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe62a490481908ee0ad4ba9a94682 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.