Triple
T27542044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 客家话 |
E695260
|
entity |
| Predicate | 罗马字方案 |
P157446
|
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: [客家话, 罗马字方案, 台湾客家语拼音方案]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 罗马字方案 Context triple: [客家话, 罗马字方案, 台湾客家语拼音方案]
-
A.
romanStatus
Indicates the status or condition of an entity within a Roman-specific context, such as its legal, social, or civic standing in Roman society.
-
B.
exampleRomanization
chosen
Indicates that one entity is a romanized representation (in Latin script) of the other entity’s original text or name.
-
C.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
D.
romanNomen
Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
-
E.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62f5ec8b481909241271f7d602dc9 |
completed | May 2, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:31 p.m.