Triple
T27328827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaguchi |
E689733
|
entity |
| Predicate | usedInFullNameOrder |
P179786
|
FINISHED |
| Object | surname-first 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: surname-first in Japanese | Statement: [Yamaguchi, usedInFullNameOrder, surname-first in Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInFullNameOrder Context triple: [Yamaguchi, usedInFullNameOrder, surname-first in Japanese]
-
A.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
B.
usedInOrder
Indicates that something (such as an item, method, or resource) is utilized or applied as part of fulfilling or processing a particular order.
-
C.
usedAfterName
Indicates that one element is used or appears immediately after a name in some context or representation.
-
D.
usedAfterNameOf
Indicates that something is used immediately following the mention or specification of a name.
-
E.
hasFullNameUsage
Indicates that an entity uses a particular full name in a specific context or manner.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727ad9ff88190ba8069dd48b2e98f |
completed | May 3, 2026, 10:47 a.m. |
Created at: April 27, 2026, 11:37 a.m.