Triple
T32185435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 勇夢 |
E822095
|
entity |
| Predicate | typicallyReadAs |
P173052
|
FINISHED |
| Object | いさむ |
—
|
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: いさむ | Statement: [勇夢, typicallyReadAs, いさむ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyReadAs Context triple: [勇夢, typicallyReadAs, いさむ]
-
A.
canonicalReading
chosen
Indicates that one representation of a text or expression is the standard or authoritative version used for reading or interpretation of another.
-
B.
commonlyReadIn
Indicates that a work is frequently read within a particular location, community, or context.
-
C.
readingOf
Indicates that one entity is an interpretation, measurement, or recorded value derived from another entity.
-
D.
readsTo
Indicates that one entity reads or recites content aloud for the benefit of another entity.
-
E.
usesReading
Indicates that one entity employs or relies on a particular reading (e.g., a text, measurement, or interpretation) in performing an action or fulfilling a function.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:35 a.m.