Triple
T7824947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakka Romanization System |
E181222
|
entity |
| Predicate | notationSystemFor |
P6517
|
FINISHED |
| Object | Hakka sounds |
—
|
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: Hakka sounds | Statement: [Hakka Romanization System, notationSystemFor, Hakka sounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notationSystemFor Context triple: [Hakka Romanization System, notationSystemFor, Hakka sounds]
-
A.
notationSystem
chosen
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
B.
notationType
Indicates the specific system or style of notation used to represent or encode something (such as music, math, or language).
-
C.
notation
Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
-
D.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
E.
representationSystem
Indicates a system or framework used to represent, encode, or symbolize information, concepts, or entities.
- 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_69ca8282ccec819083c48efb72d21cf9 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cafa0c1f5c8190b16db20daad159a1 |
completed | March 30, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69cae91ae008819098e56bbe51143b31 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:42 p.m.