Triple
T32614694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moiyan Hakka |
E833751
|
entity |
| Predicate | hasPrestigeStatusIn |
P96473
|
FINISHED |
| Object | Hakka 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: Hakka Chinese | Statement: [Moiyan Hakka, hasPrestigeStatusIn, Hakka Chinese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrestigeStatusIn Context triple: [Moiyan Hakka, hasPrestigeStatusIn, Hakka Chinese]
-
A.
isPrestigeLevel
Indicates that an entity possesses a particular status or rank associated with prestige or high standing.
-
B.
isPrestigiousIn
chosen
Indicates that an entity is widely recognized and highly regarded for excellence or status within a particular field, domain, or context.
-
C.
hasNobleStatus
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
D.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status in relation to another entity.
-
E.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
Created at: May 1, 2026, 1:06 a.m.