Triple
T28852796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cleveland Barons |
E728647
|
entity |
| Predicate | uniqueFact |
P8229
|
FINISHED |
| Object | last NHL franchise to cease operations |
—
|
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: last NHL franchise to cease operations | Statement: [Cleveland Barons, uniqueFact, last NHL franchise to cease operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: uniqueFact Context triple: [Cleveland Barons, uniqueFact, last NHL franchise to cease operations]
-
A.
notableFact
chosen
Indicates that there exists a particularly significant or noteworthy fact or piece of information associated with the subject.
-
B.
notableProductionFact
Indicates a noteworthy or distinctive fact about how something was produced, created, or manufactured.
-
C.
questionedFact
Indicates that one entity has asked about or challenged the truth, accuracy, or validity of a particular fact associated with another entity.
-
D.
fact
Indicates that something is objectively true or has actually occurred, independent of opinion or belief.
-
E.
factFinding
Indicates a process of gathering and verifying information or evidence to determine the truth about a situation or claim.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f659d9ced481908ae528169fa6cd28 |
completed | May 2, 2026, 8:08 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:44 a.m.