Triple
T20901290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superman: Man of Tomorrow |
E514671
|
entity |
| Predicate | mainCharacter |
P1183
|
FINISHED |
| Object | Lobo |
—
|
NE NERFINISHED |
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: Lobo | Statement: [Superman: Man of Tomorrow, mainCharacter, Lobo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lobo Context triple: [Superman: Man of Tomorrow, mainCharacter, Lobo]
-
A.
Lobo
Lobo is the popular nickname of Argentine football club Gimnasia y Esgrima La Plata, reflecting its fierce and combative identity.
-
B.
Lobo
Lobo is a surname most prominently associated with Rebecca Lobo, a former American professional basketball player and Hall of Famer.
-
C.
Lobo
Lobo is a coastal municipality in the province of Batangas in the Philippines, known for its beaches, dive sites, and marine biodiversity.
-
D.
Lobo
chosen
Lobo is a violent, wisecracking intergalactic bounty hunter and antihero from DC Comics known for his immense strength, regenerative abilities, and over-the-top brutality.
-
E.
Lobo
Lobo is an American soft rock singer-songwriter best known for his 1970s hits such as "Me and You and a Dog Named Boo" and "I'd Love You to Want Me."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e8fc5d488190b62f51c35e768d38 |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.