Triple
T35865215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American 3 Hockey League |
E1037066
|
entity |
| Predicate | notableDestinationLevel |
P35273
|
FINISHED |
| Object | NCAA Division III hockey |
E19
|
NE 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: NCAA Division III hockey | Statement: [North American 3 Hockey League, notableDestinationLevel, NCAA Division III hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDestinationLevel Context triple: [North American 3 Hockey League, notableDestinationLevel, NCAA Division III hockey]
-
A.
notableDestination
chosen
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
B.
notableDestinationType
Indicates the general category or type of destination for which something is considered notable.
-
C.
notableSpot
Indicates that a location is recognized as a significant or noteworthy place in some context.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
- F. None of above.
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4e8d74081908e2927b72182bf46 |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.