Triple
T4240681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ayin |
E95403
|
entity |
| Predicate | hasJoiningType |
P44434
|
FINISHED |
| Object | non-joining |
—
|
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: non-joining | Statement: [Ayin, hasJoiningType, non-joining]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJoiningType Context triple: [Ayin, hasJoiningType, non-joining]
-
A.
hasJointType
Indicates that one entity is associated with, or characterized by, a specific type or category of joint.
-
B.
hasJunctionType
Indicates the specific kind or classification of a junction associated with an entity.
-
C.
hasRightJoiningForm
Indicates that one element connects or attaches to the right side of another element in a specific form or configuration.
-
D.
hasLeftJoiningForm
Indicates that one element connects to another in such a way that the joining or continuation occurs from its left side.
-
E.
hasJoiningTypeInHebrewScript
chosen
Indicates that the relationship specifies the type of joining or connection, expressed using Hebrew script.
- 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_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. |
Created at: March 12, 2026, 11:05 p.m.