Triple
T4240647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayin |
E95403
|
entity |
| Predicate | IPATraditional |
P54885
|
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: [Ayin, IPATraditional, ʕ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPATraditional Context triple: [Ayin, IPATraditional, ʕ]
-
A.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
B.
patentIn
Indicates that one entity holds or is associated with a patent located, filed, or registered in a particular jurisdiction, organization, or context represented by the other entity.
-
C.
settingTraditional
Indicates that something is situated or occurs within a traditional setting, context, or environment.
-
D.
traditionalIdentification
Indicates that an entity is recognized or classified according to customary or historically established criteria or practices.
-
E.
traditionallyOneOf
Indicates that something is customarily or historically considered to belong to a specific set, category, or group.
- F. None of above. chosen
Provenance (4 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_69b3453d91548190b4d4ef8fe52aa2ac |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e87c9d88190a093b1289df5b974 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.