Triple
T13447719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongo |
E320526
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Mongo |
E832348
|
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: Mongo | Statement: [Mongo, nickname, Mongo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mongo Context triple: [Mongo, nickname, Mongo]
-
A.
Mongo
Mongo is the first child of Claireece "Precious" Jones in the novel and film "Precious," born with severe disabilities as a result of incestuous abuse.
-
B.
Mongo
Mongo is the nickname of Steve "Mongo" McMichael, a former NFL defensive tackle and professional wrestler best known for his time with the Chicago Bears and WCW.
-
C.
Mongo
Mongo is a major Bantu language spoken primarily in the Democratic Republic of the Congo by the Mongo people.
-
D.
Mongo
chosen
Mongo is the dim-witted but immensely strong henchman from the satirical Western comedy film "Blazing Saddles."
-
E.
MongoDB database
MongoDB database is a popular open-source NoSQL document-oriented database designed for scalability, flexibility, and high performance in modern applications.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef758b08190b9aa5ec7082cd417 |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7462340548190b156a8213f5e2556 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:41 p.m.