Triple
T28291641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yasuko |
E713441
|
entity |
| Predicate | nameSuffixUsage |
P42400
|
FINISHED |
| Object | uses the common feminine suffix -ko |
—
|
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: uses the common feminine suffix -ko | Statement: [Yasuko, nameSuffixUsage, uses the common feminine suffix -ko]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameSuffixUsage Context triple: [Yasuko, nameSuffixUsage, uses the common feminine suffix -ko]
-
A.
familyNameSuffix
Indicates that one entity is the suffix portion (such as “Jr.” or “III”) of another entity’s family name.
-
B.
possibleSurnameUsage
Indicates that an entity can potentially be used or recognized as a surname for another entity.
-
C.
nameEnding
Indicates that one entity’s name ends with the string or substring represented by the other entity.
-
D.
surnameUsedIn
Indicates that a particular surname is used or borne within a specified context, such as by a person, family, or group.
-
E.
usedAsSuffixTo
chosen
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 11:29 p.m.