Triple
T30640083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 加藤氏 |
E779949
|
entity |
| Predicate | hasDomainAssociation |
P176754
|
FINISHED |
| Object | 肥後熊本藩 |
—
|
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: 肥後熊本藩 | Statement: [加藤氏, hasDomainAssociation, 肥後熊本藩]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainAssociation Context triple: [加藤氏, hasDomainAssociation, 肥後熊本藩]
-
A.
hasAssociatedAuthority
Indicates that an entity is linked to a specific authority that holds responsibility, control, or oversight related to it.
-
B.
hasDomainZone
Indicates that one entity possesses, controls, or is associated with a specific domain zone within a larger domain or namespace.
-
C.
hasPossibleDomain
Indicates that a property or relation may apply to, or be defined over, a particular class or type of entities, without asserting that this is its only or actual domain.
-
D.
containsDomain
Indicates that one entity includes or encompasses a specific domain as part of its scope, structure, or area of applicability.
-
E.
hasNumberOfDomains
Indicates the specific count of distinct domains associated with an entity.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 29, 2026, 8:29 p.m.