Triple
T34040036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 健太郎 |
E872913
|
entity |
| Predicate | nameEndingAssociation |
P103831
|
FINISHED |
| Object | traditional masculine name ending in Japanese |
—
|
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: traditional masculine name ending in Japanese | Statement: [健太郎, nameEndingAssociation, traditional masculine name ending in Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameEndingAssociation Context triple: [健太郎, nameEndingAssociation, traditional masculine name ending in Japanese]
-
A.
nameEnding
chosen
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
B.
associatedSurname
Indicates that one entity has a surname that is linked or connected to another entity, such as a person, family, or name record.
-
C.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
D.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
-
E.
endName
Indicates that one entity serves as the ending or final name/designation associated with another entity.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.