Triple
T23720375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 数子 |
E586125
|
entity |
| Predicate | nameElement-子 |
P37982
|
FINISHED |
| Object | common feminine name suffix 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: common feminine name suffix in Japanese | Statement: [数子, nameElement-子, common feminine name suffix in Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameElement-子 Context triple: [数子, nameElement-子, common feminine name suffix in Japanese]
-
A.
nameElement
Indicates that one entity serves as the name or label assigned to another entity or element.
-
B.
nameElementIn
chosen
Indicates that an entity is (or contains) a specific name element within a larger naming structure or system.
-
C.
nameElements
Indicates that an entity assigns or specifies the names of multiple elements within a set or structure.
-
D.
basedOnElementName
Indicates that one entity is derived from, determined by, or otherwise depends on the name of another element.
-
E.
childName
Indicates that one entity is the name (or given name) of a child associated with 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_69e24906fb108190a6898751e46bdc11 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b910759c8190be189db3e86d7258 |
completed | April 29, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7 p.m.