Triple
T1575973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taro |
E33651
|
entity |
| Predicate | nameSuffixRole |
P341
|
FINISHED |
| Object | can appear as a suffix in male 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: can appear as a suffix in male given names | Statement: [Taro, nameSuffixRole, can appear as a suffix in male given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameSuffixRole Context triple: [Taro, nameSuffixRole, can appear as a suffix in male given names]
-
A.
honorificSuffix
chosen
Indicates that one entity is a respectful or formal suffix appended to another entity’s name or title.
-
B.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
C.
nameType
Indicates the specific category or type of a name associated with an entity (e.g., legal name, nickname, alias, or preferred name).
-
D.
registrationSuffix
Indicates the trailing part or extension added to a base registration identifier to form a complete registration code.
-
E.
designationType
Indicates the specific category or kind of formal status, title, or label that has been assigned in a designation relationship.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.