Triple
T34614116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qinwang (Prince of the First Rank) |
E888815
|
entity |
| Predicate | rankInQingNobility |
P66828
|
FINISHED |
| Object | highest princely rank |
—
|
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: highest princely rank | Statement: [Qinwang (Prince of the First Rank), rankInQingNobility, highest princely rank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankInQingNobility Context triple: [Qinwang (Prince of the First Rank), rankInQingNobility, highest princely rank]
-
A.
nobleRankOf
Indicates that one entity holds a specific noble title or rank within a hierarchical nobility system.
-
B.
nobleRankAbove
Indicates that one entity holds a higher noble rank or title in a hierarchy than another entity.
-
C.
nobleRankIn
chosen
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
D.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
E.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
- 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_69f349d584e08190b40b9f6281ad50c4 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 2:03 a.m.