Triple
T5295260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Mikan |
E119837
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mikan |
E119832
|
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: Mikan | Statement: [George Mikan, familyName, Mikan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikan Context triple: [George Mikan, familyName, Mikan]
-
A.
Mikan
chosen
Mikan is a surname most famously associated with George Mikan, a pioneering American professional basketball player often regarded as the NBA’s first dominant big man.
-
B.
Miki
Miki is a city in Japan located within Hyogo Prefecture, known for its traditional hardware industry and historical sites.
-
C.
Maki
Maki is a Japanese surname most notably associated with Fumihiko Maki, a prominent modernist architect known for his innovative urban and architectural designs.
-
D.
Maki
Maki is an Israeli communist political party historically associated with figures such as Meir Vilner and the broader leftist movement in Israel.
-
E.
Michishio
Michishio was a Japanese Navy destroyer that served in World War II and was sunk during the Battle of Surigao Strait in 1944.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd84f19d048190a826f51acc603544 |
completed | March 20, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf10e3a0908190895fb4442afc715e |
completed | March 21, 2026, 9:42 p.m. |
Created at: March 20, 2026, 1:52 p.m.