Triple
T33692003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese imperial court |
E863207
|
entity |
| Predicate | selectionMethodForOfficials |
P178662
|
FINISHED |
| Object | imperial examination system |
—
|
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: imperial examination system | Statement: [Chinese imperial court, selectionMethodForOfficials, imperial examination system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionMethodForOfficials Context triple: [Chinese imperial court, selectionMethodForOfficials, imperial examination system]
-
A.
judgesSelectionMethod
Indicates that a judge or judging body uses a particular method or criteria to evaluate and select among options or candidates.
-
B.
winnerSelectionMethod
Indicates the process or criteria used to determine which participant is chosen as the winner.
-
C.
jurySelectionMethod
Indicates the process or criteria used to choose individuals who will serve on a jury.
-
D.
teamSelectionAuthority
Indicates that an entity has the authority or responsibility to choose or determine the members of a team.
-
E.
delegateSelectionMethod
Indicates the method or process by which responsibility or authority is assigned from one entity to another.
- 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_69f3498662b48190904442c39df84fb7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f713bfdc148190a249a7874320bab8 |
completed | May 3, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f7135fa2988190a20a94cfe616d754 |
completed | May 3, 2026, 9:20 a.m. |
Created at: May 1, 2026, 1:43 a.m.