Triple
T18792246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union College Dutchmen and Dutchwomen |
E459543
|
entity |
| Predicate | iceHockeyCharacteristic |
P133037
|
FINISHED |
| Object | intense regional rivalries |
—
|
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: intense regional rivalries | Statement: [Union College Dutchmen and Dutchwomen, iceHockeyCharacteristic, intense regional rivalries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iceHockeyCharacteristic Context triple: [Union College Dutchmen and Dutchwomen, iceHockeyCharacteristic, intense regional rivalries]
-
A.
iceSurface
Indicates that something is located on, in contact with, or forming the surface of ice.
-
B.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
C.
iceHockeyFormat
Indicates that the subject is associated with or uses a particular format, structure, or rule set specific to ice hockey.
-
D.
usesStandardIceRink
Indicates that the activity, event, or entity operates on or is conducted within a regulation-size, standard ice rink.
-
E.
typeOfHockey
Indicates a relationship where one entity is classified as a specific kind or variant of hockey.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5978665388190aaefed0ec30a1ff3 |
completed | April 20, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e49785fd7081909577e90a55df0a35 |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:53 a.m.