Triple
T12250686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moe |
E291961
|
entity |
| Predicate | name |
P16
|
FINISHED |
| Object | Moe |
unclear NED1
|
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: Moe | Statement: [Moe, name, Moe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moe Context triple: [Moe, name, Moe]
-
A.
Moe
Moe is the nickname of Moe Berg, an American baseball player who famously served as a spy during World War II.
-
B.
Moe
Moe is a kangaroo character known by the name Moe.
-
C.
Moe
Moe is a surname most notably associated with various American figures in sports, entertainment, and public life.
-
D.
Moe Gale
Moe Gale was a prominent American music producer and talent manager known for his influential role in the development of swing and big band jazz in the mid-20th century.
-
E.
Mighty Mo
Mighty Mo is the famous nickname of the USS Missouri, a U.S. Navy battleship best known as the site of Japan’s formal surrender in World War II.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc6983c81909bf479d15879a357 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60abbf75c81908a25e1c0a4aee8c1 |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:52 p.m.