Triple
T13378726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beth-togarmah |
E319258
|
entity |
| Predicate | TogarmahDescribedAs |
P109684
|
FINISHED |
| Object | descendant of Gomer |
—
|
LITERAL 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: descendant of Gomer | Statement: [Beth-togarmah, TogarmahDescribedAs, descendant of Gomer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TogarmahDescribedAs Context triple: [Beth-togarmah, TogarmahDescribedAs, descendant of Gomer]
-
A.
hasTamga
Indicates that an entity bears or is marked with a specific tamga (a distinctive emblem, brand, or clan/ownership mark).
-
B.
roleInMonsterVerse
Indicates that an entity has a specific role or function within the MonsterVerse franchise or universe.
-
C.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
D.
eraCharacter
Indicates that a character is associated with, or belongs to, a particular historical or fictional era.
-
E.
MongolianCommander
Indicates that an individual holds a commanding or leadership role within a Mongolian military or armed force context.
- F. None of above. chosen
Provenance (4 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dadce56c6c8190adf4e19f6d1bc233 |
completed | April 11, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:33 p.m.