Triple
T26168528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fumi |
E654328
|
entity |
| Predicate | isNameElementIn |
P37982
|
FINISHED |
| Object | masculine 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: masculine Japanese given names | Statement: [Fumi, isNameElementIn, masculine Japanese given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNameElementIn Context triple: [Fumi, isNameElementIn, masculine Japanese given names]
-
A.
includesElement
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
B.
nameElementIn
chosen
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
C.
hasNameElementType
Indicates that something includes a specific type or category of element within its name.
-
D.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
E.
basedOnElementName
Indicates that one entity is derived from, determined by, or otherwise depends on the name of another element.
- 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_69ee5b44391c81908bdbd8813ba9aa99 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c4132a88190ba74c1c290cbe35d |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:34 p.m.