Triple
T17504250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naoyoshi |
E426269
|
entity |
| Predicate | isNotFamilyName |
P127700
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Naoyoshi, isNotFamilyName, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNotFamilyName Context triple: [Naoyoshi, isNotFamilyName, true]
-
A.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
B.
hasUnknownFamilyName
Indicates that an entity’s family name is not known or has not been specified.
-
C.
hasNameInFamily
Indicates that an entity is known or referred to by a particular name within the context of a specific family or familial group.
-
D.
canBeFamilyName
Indicates that something is capable of functioning as a family name or surname in at least one context.
-
E.
isOriginalFamilyNameOf
Indicates that a given family name is the original or birth surname of a person, from which any later or changed surnames may have derived.
- 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e45214d44c8190b1bf04bf24ab8e81 |
completed | April 19, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f5fbcc8190a6ea9639bf5650da |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:48 a.m.