Triple
T3338184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleston Historic District |
E70190
|
entity |
| Predicate | dateDesignatedNHL |
P19616
|
FINISHED |
| Object | 1960-11-07 |
—
|
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: 1960-11-07 | Statement: [Charleston Historic District, dateDesignatedNHL, 1960-11-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateDesignatedNHL Context triple: [Charleston Historic District, dateDesignatedNHL, 1960-11-07]
-
A.
NHLDesignationDate
chosen
Indicates the date on which something was officially designated or recognized by the NHL.
-
B.
NHLDesignationYear
Indicates the year in which an entity received its official National Historic Landmark (NHL) designation.
-
C.
nhlDebutSeason
Indicates the season in which a person first played in a National Hockey League (NHL) game.
-
D.
NHLTeamNumberRetiredBy
Indicates that a specific jersey number has been officially retired by a particular NHL team in honor of a player or significant figure.
-
E.
joinedNHL
Indicates that an entity became a member of, or started playing in, the National Hockey League (NHL).
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bc31b4819085f01e0b5a7cbc5d |
completed | March 8, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69ada42c2ba8819091136805ce17b39d |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.