Triple
T7416268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maeda clan |
E171137
|
entity |
| Predicate | rankWithinDaimyo |
P9684
|
FINISHED |
| Object | second only to the Tokugawa in wealth |
—
|
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: second only to the Tokugawa in wealth | Statement: [Maeda clan, rankWithinDaimyo, second only to the Tokugawa in wealth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankWithinDaimyo Context triple: [Maeda clan, rankWithinDaimyo, second only to the Tokugawa in wealth]
-
A.
nobleRankIn
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
B.
honorificRank
Indicates that one entity holds a formal title or honorific status in relation to another entity.
-
C.
rankRelativeToPeerage
chosen
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
D.
shrineRank
Indicates the hierarchical or status level assigned to a shrine relative to other shrines.
-
E.
namedForRank
Indicates that something is named after a specific rank or title held by an 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c7ae0c8190a8348d6223aeeecc |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.