Triple
T22382502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asano clan |
E553309
|
entity |
| Predicate | domainStipend |
P147449
|
FINISHED |
| Object | about 426,500 koku in Hiroshima Domain |
—
|
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: about 426,500 koku in Hiroshima Domain | Statement: [Asano clan, domainStipend, about 426,500 koku in Hiroshima Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainStipend Context triple: [Asano clan, domainStipend, about 426,500 koku in Hiroshima Domain]
-
A.
domainServed
Indicates that a particular domain or area is supported, covered, or provided for by a given entity or service.
-
B.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
C.
laterDomain
Indicates that one domain or time interval occurs strictly after another in a temporal ordering.
-
D.
typicalDomain
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
E.
creativeDomain
Indicates the domain or field of creative activity within which an entity produces or expresses its work.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1582cce608190b5324b30f349a3ff |
completed | April 29, 2026, 1 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e73597b51c8190aeff27f4779b82f3 |
completed | April 21, 2026, 8:30 a.m. |
Created at: April 16, 2026, 8:45 p.m.