Triple
T28916349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aki |
E733376
|
entity |
| Predicate | usedAsNameComponentIn |
P32965
|
FINISHED |
| Object | longer Japanese 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: longer Japanese given names | Statement: [Aki, usedAsNameComponentIn, longer Japanese given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsNameComponentIn Context triple: [Aki, usedAsNameComponentIn, longer Japanese given names]
-
A.
usedAsNameSourceFor
Indicates that one entity serves as the origin or basis from which another entity’s name is derived.
-
B.
usedInNamingPractice
Indicates that something serves as a basis, source, or reference in the practice of assigning names.
-
C.
usedInFullNameOf
chosen
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.
-
D.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
E.
usedInCompoundNames
Indicates that one entity’s name is employed as a component within the compound name of 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 8:15 a.m.