Triple
T27971439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Jin |
E706366
|
entity |
| Predicate | rankWithinImperialClan |
P148206
|
FINISHED |
| Object | imperial prince |
—
|
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 prince | Statement: [Prince of Jin, rankWithinImperialClan, imperial prince]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinImperialClan Context triple: [Prince of Jin, rankWithinImperialClan, imperial prince]
-
A.
clanChiefRank
Indicates that the subject holds the rank or position of chief within a clan in relation to the object.
-
B.
rankWithinTokugawa
Indicates the relative hierarchical position or status an entity holds within the Tokugawa-era ranking system.
-
C.
rankRelativeToDaijō-daijin
Indicates the relative hierarchical rank or status of an entity in comparison to the position of Daijō-daijin (Chancellor of the Realm).
-
D.
rulingClanOf
Indicates that one clan holds ruling or governing authority over another group, territory, or domain.
-
E.
rankWithinImperialFamily
chosen
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b35079c819084779003fe29410d |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f63710d17c819084cfe96e6df334fd |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:38 p.m.