Triple
T3437026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hartford Wolf Pack |
E72477
|
entity |
| Predicate | usedNameToYear |
P48251
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Hartford Wolf Pack, usedNameToYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedNameToYear Context triple: [Hartford Wolf Pack, usedNameToYear, 2013]
-
A.
originalNameUsedInYears
Indicates that a particular original name was in use for an entity during a specified range of years.
-
B.
originYear
Indicates the year in which something first originated, was created, or began.
-
C.
lastEditionYearUnderThisName
Indicates the final year in which something (such as a publication, event, or product) was issued or held under a specific name before that name changed or was discontinued.
-
D.
firstYearUnderCurrentName
Indicates the first year in which an entity began operating or being known under its current name.
-
E.
formerNamePeriodStart
Indicates the date or time point when an entity began using a former name that is being recorded.
- 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_69ad85af50288190a854b76653deee6f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9f4398c8190a75822068308037b |
completed | March 8, 2026, 6:03 p.m. |
| PD | Predicate disambiguation | batch_69adae00ad588190bef24373b58a2e1a |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adaed74ecc8190b74dc70ab59a3e1c |
completed | March 8, 2026, 5:16 p.m. |
Created at: March 8, 2026, 3:16 p.m.