Triple
T9713351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RWZ |
E235074
|
entity |
| Predicate | airlineCallsign |
P13478
|
FINISHED |
| Object | RED WINGS |
E236115
|
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: RED WINGS | Statement: [RWZ, airlineCallsign, RED WINGS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RED WINGS Context triple: [RWZ, airlineCallsign, RED WINGS]
-
A.
RED WINGS
chosen
RED WINGS is the radio callsign used by Red Wings Airlines, a Russian passenger airline.
-
B.
Red Wings
Red Wings is the nickname of the Rochester Red Wings, a long-standing Minor League Baseball team based in Rochester, New York.
-
C.
Galt Red Wings
The Galt Red Wings were a Canadian junior ice hockey team based in Galt, Ontario, that competed in the Ontario Hockey Association.
-
D.
Detroit Red Wings
The Detroit Red Wings are a historic NHL franchise based in Detroit, Michigan, renowned as one of the league’s Original Six teams and for their multiple Stanley Cup championships.
-
E.
Hamilton Tigers
The Hamilton Tigers were an early 20th-century Canadian professional ice hockey team that competed in the National Hockey League before folding in the mid-1920s.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e087a1c8190aa62c910f88e8516 |
completed | April 1, 2026, 10:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19f8c26dc8190a6fa21bde27ba6fa |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:19 p.m.