Triple
T7229291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ṣād |
E154862
|
entity |
| Predicate | secondaryArticulation |
P6870
|
FINISHED |
| Object | pharyngealized |
—
|
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: pharyngealized | Statement: [Ṣād, secondaryArticulation, pharyngealized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryArticulation Context triple: [Ṣād, secondaryArticulation, pharyngealized]
-
A.
hasArticulation
Indicates that one entity possesses or exhibits a specific type or structure of articulation in relation to another entity or system.
-
B.
usesArticulators
Indicates that an entity performs an action or produces a signal by employing specific speech or movement articulators (e.g., tongue, lips, jaw).
-
C.
articulated
Indicates that one entity has expressed, formulated, or clearly stated another entity (such as an idea, plan, or position) in words or another communicative form.
-
D.
secondaryPosition
chosen
Indicates that an entity holds an additional, non-primary role, location, or status alongside its main one.
-
E.
articulatedWith
Indicates that two parts are connected by a joint or mechanism that allows controlled movement between them.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9e0ba248190a57a3b4fa8b858c7 |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.