Triple
T19646374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | زَيْن |
E471681
|
entity |
| Predicate | يُنطق |
P85531
|
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.
cannotBeEasilySpokenBy
Indicates that one entity (typically a word, phrase, or name) is difficult for another entity (typically a speaker or group) to pronounce or articulate smoothly.
-
B.
correctPronunciation
chosen
Indicates that one entity provides the accurate or standard way to pronounce another entity (such as a word or name).
-
C.
isMorePronouncedIn
Indicates that a particular feature, quality, or effect appears with greater intensity or prominence in one context, entity, or condition than in another.
-
D.
typeOfPronunciationDescribed
Indicates that one entity specifies or characterizes the kind or style of pronunciation associated with another entity.
-
E.
spokenOfAs
Indicates that one entity is referred to, characterized, or talked about in a particular way by another entity or within a given context.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641250e108190a707452fefc87041 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.