Triple
T33941215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Later Toba |
E870168
|
entity |
| Predicate | hasEarlierNamesake |
P177946
|
FINISHED |
| Object | Emperor Toba |
—
|
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: Emperor Toba | Statement: [Later Toba, hasEarlierNamesake, Emperor Toba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarlierNamesake Context triple: [Later Toba, hasEarlierNamesake, Emperor Toba]
-
A.
hasModernNamesake
Indicates that an entity is the namesake or inspiration for a modern entity that shares or derives its name from it.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
hasNamedAfterPerson
Indicates that one entity is named in honor of, or derived from the name of, a specific person.
-
D.
hasNamesakeRoleInHistory
Indicates that an entity has a historical role or position that is the same as, or named after, another entity’s role in history.
-
E.
hasTitleNamesake
Indicates that one entity serves as the namesake or source of the title borne by another entity.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f7064d37388190993b2a7305a02b9f |
completed | May 3, 2026, 8:24 a.m. |
Created at: May 1, 2026, 1:49 a.m.