Triple
T16412160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wanyan Aguda |
E398591
|
entity |
| Predicate | militaryRankBeforeEmperorship |
P80252
|
FINISHED |
| Object | Jurchen chieftain |
—
|
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: Jurchen chieftain | Statement: [Wanyan Aguda, militaryRankBeforeEmperorship, Jurchen chieftain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryRankBeforeEmperorship Context triple: [Wanyan Aguda, militaryRankBeforeEmperorship, Jurchen chieftain]
-
A.
militaryRankBeforeAccession
chosen
Indicates the military rank held by an individual prior to their accession to a particular office, position, or status.
-
B.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
C.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
D.
titleBeforeEmperor
Indicates that one entity held a particular title or rank prior to becoming emperor.
-
E.
militaryRankOfPrecedence
Indicates the relative seniority or priority order of a military rank compared to other ranks.
- F. None of above.
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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32874a0cc8190874aea10b1d13004 |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.