Triple
T7270954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hirofumi |
E161100
|
entity |
| Predicate | belongsToOnomasticCategory |
P22351
|
FINISHED |
| Object | Japanese masculine given names |
—
|
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: Japanese masculine given names | Statement: [Hirofumi, belongsToOnomasticCategory, Japanese masculine given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOnomasticCategory Context triple: [Hirofumi, belongsToOnomasticCategory, Japanese masculine given names]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasOnomasticField
chosen
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
C.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
D.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
-
E.
containsCategory
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69c6885181008190b419040e22939c7c |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6eb8a0b4881908ff27c5a75bd4a95 |
completed | March 27, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69c6e76a84a081908d4184c55b728e48 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:58 p.m.