Triple
T32048443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yen |
E818416
|
entity |
| Predicate | romanizationOfDialect |
P165754
|
FINISHED |
| Object | Mandarin Chinese |
—
|
NE NERFINISHED |
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: Mandarin Chinese | Statement: [Yen, romanizationOfDialect, Mandarin Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanizationOfDialect Context triple: [Yen, romanizationOfDialect, Mandarin Chinese]
-
A.
romanizationVariantOf
Indicates that one written form is a different romanized representation of the same underlying word or expression as another.
-
B.
romanizationType
Indicates the specific system or method used to convert text from one writing system into its Roman (Latin) alphabet representation.
-
C.
romanizationRegion
chosen
Indicates the region or locale whose conventions are used to romanize a name, term, or text.
-
D.
romanizationFrom
Indicates that one entity is a romanized representation derived from the script or writing system of another entity.
-
E.
romanizationOfToponymType
Indicates a relationship where a specific type of place-name is expressed in a romanized (Latin-script) form corresponding to its original writing system.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f71996e1a48190ac59a1d66d7c44e8 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 12:20 a.m.