Triple
T23673775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shimazu clan |
E584809
|
entity |
| Predicate | stipendRank |
P152933
|
FINISHED |
| Object | one of the largest domains in Edo period Japan |
—
|
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: one of the largest domains in Edo period Japan | Statement: [Shimazu clan, stipendRank, one of the largest domains in Edo period Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stipendRank Context triple: [Shimazu clan, stipendRank, one of the largest domains in Edo period Japan]
-
A.
grantsRank
Indicates that one entity confers or assigns a particular rank, status, or level to another entity.
-
B.
eligibleRank
Indicates that an entity meets the required rank or level criteria to qualify for a specific role, action, or benefit.
-
C.
positionInScholarship
Indicates the specific role, rank, or standing that an entity holds within a particular scholarship or scholarship program.
-
D.
approximateStipend
Indicates an estimated or rough amount of stipend associated with an entity or situation.
-
E.
isRanked
Indicates that an entity has been assigned a position or level within an ordered hierarchy or comparative list.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f1dee08190bfe78564c65f01ad |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:51 p.m.