Triple
T7592998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 太郎 |
E179784
|
entity |
| Predicate | hasGivenNamePosition |
P1082
|
FINISHED |
| Object | first name in Western order |
—
|
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: first name in Western order | Statement: [太郎, hasGivenNamePosition, first name in Western order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNamePosition Context triple: [太郎, hasGivenNamePosition, first name in Western order]
-
A.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
-
B.
namePosition
chosen
Indicates the positional or ordering relationship of a name within a sequence or structured context (e.g., first, last, or specific index).
-
C.
hasGivenNameBasis
Indicates that one entity’s given name is derived from, based on, or formed using another entity (such as a name, word, or person) as its basis.
-
D.
hasUnknownGivenName
Indicates that the given (first) name of the entity is not known or not specified.
-
E.
hasProperName
Indicates that an entity is associated with a specific proper name used to uniquely identify it.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9b92c348190b547f0aacfb8d6be |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.