Triple
T5690709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale Cantonese |
E125420
|
entity |
| Predicate | hasTranscriptionGoal |
P38988
|
FINISHED |
| Object | phonemic representation of Cantonese |
—
|
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: phonemic representation of Cantonese | Statement: [Yale Cantonese, hasTranscriptionGoal, phonemic representation of Cantonese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTranscriptionGoal Context triple: [Yale Cantonese, hasTranscriptionGoal, phonemic representation of Cantonese]
-
A.
hasLinguisticGoal
chosen
Indicates that an entity is associated with or directed toward achieving a particular linguistic objective or outcome.
-
B.
transcription
Indicates the process by which genetic information in DNA is copied into RNA by RNA polymerase.
-
C.
hasPrimaryGoal
Indicates that an entity’s main or most important objective is the specified goal.
-
D.
hasTherapeuticGoal
Indicates that an action, treatment, or intervention is undertaken with the intention of achieving a specific therapeutic or health-related outcome.
-
E.
hasResearchGoal
Indicates that an entity has a specific research objective, aim, or target it is pursuing or designed to address.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.