Triple
T38169711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hezhenyu |
E1000036
|
entity |
| Predicate | spokenByGenerations |
P14809
|
FINISHED |
| Object | primarily elderly speakers |
—
|
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: primarily elderly speakers | Statement: [Hezhenyu, spokenByGenerations, primarily elderly speakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenByGenerations Context triple: [Hezhenyu, spokenByGenerations, primarily elderly speakers]
-
A.
spokenByGeneration
chosen
Indicates that something (such as a statement, text, or utterance) is spoken or produced vocally by a particular generation or age cohort.
-
B.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
C.
spokenInDecade
Indicates that something (typically a speech, phrase, or linguistic usage) was spoken or used during a particular decade.
-
D.
voicedByAlsoKnownFor
Indicates that the person who voices a character is also notably recognized for another specific role or work.
-
E.
refersToGeneration
Indicates that one entity is associated with, or designates, a particular generation or age cohort of another entity.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fcb089a8f881909aa9e722babd43f7 |
completed | May 7, 2026, 3:32 p.m. |
| PD | Predicate disambiguation | batch_69fc45666c5c8190913bd632ac0e5b84 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:29 p.m.