Triple
T15518304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Mo |
E368888
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Mighty Mo |
E75656
|
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: Mighty Mo | Statement: [Big Mo, alsoKnownAs, Mighty Mo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mighty Mo Context triple: [Big Mo, alsoKnownAs, Mighty Mo]
-
A.
Mighty Mo
chosen
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.
-
B.
Moxley Moxx
Moxley Moxx is an early ring name used by the American professional wrestler better known today as Jon Moxley (formerly Dean Ambrose in WWE).
-
C.
Moe
Moe is the nickname of Moe Berg, an American baseball player who famously served as a spy during World War II.
-
D.
Moe
Moe is a kangaroo character known by the name Moe.
-
E.
Moe
Moe is a surname most notably associated with various American figures in sports, entertainment, and public life.
- 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_69d85a1794cc8190b0b428716296e63e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e040343d9c8190a7d1f197c108bd9d |
completed | April 16, 2026, 1:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff3d52cf1c8190b18bff0b925355a3 |
completed | May 9, 2026, 1:57 p.m. |
Created at: April 10, 2026, 4:03 a.m.