Triple
T14427619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jebe |
E357735
|
entity |
| Predicate | rank |
P268
|
FINISHED |
| Object |
noyan
Noyan was a high-ranking Mongol military title, roughly equivalent to a general or noble commander, used in the Mongol Empire.
|
E1099895
|
NE FINISHED |
How this triple was built (4 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: noyan | Statement: [Jebe, rank, noyan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: noyan Context triple: [Jebe, rank, noyan]
-
A.
nyoin
Nyoin was an honorific title in Japan historically granted to imperial women, particularly empresses and high-ranking consorts, who were accorded quasi-monastic and elevated courtly status.
-
B.
nyn
nyn is the ISO 639 language code for Runyankole, a Bantu language spoken primarily in southwestern Uganda.
-
C.
no-miya
no-miya is a Japanese imperial princely title historically used for certain collateral branches of the Imperial Family.
-
D.
NOH
NOH was the former abbreviation used for the New Orleans Hornets NBA franchise before it was rebranded as the New Orleans Pelicans.
-
E.
nan
nan is the ISO 639-3 language code assigned to the Teochew (Chaoshan) Chinese language variety spoken primarily in eastern Guangdong, China, and among overseas Chinese communities.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: noyan Triple: [Jebe, rank, noyan]
Generated description
Noyan was a high-ranking Mongol military title, roughly equivalent to a general or noble commander, used in the Mongol Empire.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: noyan Target entity description: Noyan was a high-ranking Mongol military title, roughly equivalent to a general or noble commander, used in the Mongol Empire.
-
A.
nyoin
Nyoin was an honorific title in Japan historically granted to imperial women, particularly empresses and high-ranking consorts, who were accorded quasi-monastic and elevated courtly status.
-
B.
nyn
nyn is the ISO 639 language code for Runyankole, a Bantu language spoken primarily in southwestern Uganda.
-
C.
no-miya
no-miya is a Japanese imperial princely title historically used for certain collateral branches of the Imperial Family.
-
D.
NOH
NOH was the former abbreviation used for the New Orleans Hornets NBA franchise before it was rebranded as the New Orleans Pelicans.
-
E.
nan
nan is the ISO 639-3 language code assigned to the Teochew (Chaoshan) Chinese language variety spoken primarily in eastern Guangdong, China, and among overseas Chinese communities.
- F. None of above. chosen
Provenance (5 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de911398f08190be85bc0a8bef6b1b |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bcfa1d88190b59cefd3e305f55f |
completed | May 8, 2026, 3:43 a.m. |
| NEDg | Description generation | batch_69fd5d6af9ac8190a37f11b0f8a1db0f |
completed | May 8, 2026, 3:50 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fd5df48f7481909764bc4e23c0b04a |
completed | May 8, 2026, 3:52 a.m. |
Created at: April 10, 2026, 1:18 a.m.