Triple
T7764186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Sutter |
E176102
|
entity |
| Predicate | sibling |
P363
|
FINISHED |
| Object | Gary Sutter |
E685109
|
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: Gary Sutter | Statement: [Brian Sutter, sibling, Gary Sutter]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gary Sutter Context triple: [Brian Sutter, sibling, Gary Sutter]
-
A.
Gary Sutter
chosen
Gary Sutter is a member of the prominent Sutter family associated with professional ice hockey.
-
B.
Rich Sutter
Rich Sutter is a former Canadian professional ice hockey winger who played in the NHL and is part of the well-known Sutter hockey family.
-
C.
Bob Suter
Bob Suter was an American defenseman best known as a member of the "Miracle on Ice" 1980 U.S. Olympic hockey team and later a prominent youth hockey coach and scout.
-
D.
Joe Suter
Joe Suter is an individual notable enough to be recognized as a bearer of the surname Suter, though specific widely known achievements or roles are not clearly documented.
-
E.
Joe Sutter
Joe Sutter was an American aerospace engineer best known as the chief designer of the Boeing 747, one of the most iconic and influential commercial airliners in history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c69962923c8190ac74d28b4f9fe0a0 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c704076ba08190bcde971f7e4448c6 |
completed | March 27, 2026, 10:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c95ffa6a3c819089aa939b164dbcaa |
completed | March 29, 2026, 5:23 p.m. |
Created at: March 27, 2026, 4:09 p.m.