Triple
T27025194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCHA Men's Ice Hockey Tournament |
E680764
|
entity |
| Predicate | initiallyHeldIn |
P105721
|
FINISHED |
| Object | early 1970s |
—
|
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: early 1970s | Statement: [CCHA Men's Ice Hockey Tournament, initiallyHeldIn, early 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyHeldIn Context triple: [CCHA Men's Ice Hockey Tournament, initiallyHeldIn, early 1970s]
-
A.
firstHeldAs
Indicates the initial time or context in which an entity was first possessed, owned, or held by another entity.
-
B.
hasBeenHeldBy
Indicates that an entity has previously possessed, controlled, or occupied another entity for some duration in the past.
-
C.
hasPreviouslyBeenHeldIn
Indicates that an entity was located, confined, or kept in a particular place or container at some time in the past.
-
D.
isHeldAt
chosen
Indicates that an event, state, or condition occurs or is in effect at a specific time or temporal point.
-
E.
lastHeldIn
Indicates that an event or state most recently took place or was hosted in a particular location or context.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 7:10 a.m.