Triple
T16591387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ejei Khan |
E403093
|
entity |
| Predicate | politicalStatusAfterSurrender |
P86247
|
FINISHED |
| Object | Qing noble |
—
|
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: Qing noble | Statement: [Ejei Khan, politicalStatusAfterSurrender, Qing noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusAfterSurrender Context triple: [Ejei Khan, politicalStatusAfterSurrender, Qing noble]
-
A.
politicalStatusAfterEvent
chosen
Indicates the political status or condition an entity holds as a result of, or following, a specific event.
-
B.
politicalStatusAtEnd
Indicates the political status or condition an entity holds at the conclusion of a specified event or time period.
-
C.
legalStatusAfterCoup
Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
-
D.
legalStatusAfterEscape
Indicates the legal status or condition assigned to an individual after they have escaped from custody, confinement, or lawful control.
-
E.
politicalStatusBefore
Indicates the political status or condition an entity held prior to a specified event, change, or reference point.
- 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_69d88387363c8190a97a0c942130de97 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e359a012e081909a0604dde3c04bbb |
completed | April 18, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e296a7d9d0819088555bca6c936e79 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.